Need help
by Orion Poplawski
I'm trying to get truth 1.0.1 to build in the buildroot, but it's having
a test failure:
[ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
0.01 s <<< FAILURE! - in
com.google.common.truth.CorrespondenceExceptionStoreTest
[ERROR]
com.google.common.truth.CorrespondenceExceptionStoreTest.describeAsMainCause_notEmpty
Time elapsed: 0.009 s <<< FAILURE!
com.google.common.truth.AssertionErrorWithFacts:
expected to match:
compare\(null, 123\) threw java.lang.NullPointerException\s+at
com\.google\.common\.truth\.TestCorrespondences(.|\n)*\n---
but was:
compare(null, 123) threw java.lang.NullPointerException: Cannot
invoke "java.lang.Integer.intValue()" because "actual" is null
at
com.google.common.truth.TestCorrespondences$3.apply(TestCorrespondences.java:77)
at
com.google.common.truth.TestCorrespondences$3.apply(TestCorrespondences.java:74)
at
com.google.common.truth.Correspondence$FromBinaryPredicate.compare(Correspondence.java:150)
at
com.google.common.truth.Correspondence$FormattingDiffs.compare(Correspondence.java:389)
---
at
com.google.common.truth.CorrespondenceExceptionStoreTest.assertExpectedFacts(CorrespondenceExceptionStoreTest.java:106)
at
com.google.common.truth.CorrespondenceExceptionStoreTest.describeAsMainCause_notEmpty(CorrespondenceExceptionStoreTest.java:64)
[ERROR]
com.google.common.truth.CorrespondenceExceptionStoreTest.describeAsAdditionalInfo_notEmpty
Time elapsed: 0 s <<< FAILURE!
com.google.common.truth.AssertionErrorWithFacts:
expected to match:
compare\(null, 123\) threw java.lang.NullPointerException\s+at
com\.google\.common\.truth\.TestCorrespondences(.|\n)*\n---
but was:
compare(null, 123) threw java.lang.NullPointerException: Cannot
invoke "java.lang.Integer.intValue()" because "actual" is null
at
com.google.common.truth.TestCorrespondences$3.apply(TestCorrespondences.java:77)
at
com.google.common.truth.TestCorrespondences$3.apply(TestCorrespondences.java:74)
at
com.google.common.truth.Correspondence$FromBinaryPredicate.compare(Correspondence.java:150)
at
com.google.common.truth.Correspondence$FormattingDiffs.compare(Correspondence.java:389)
---
at
com.google.common.truth.CorrespondenceExceptionStoreTest.assertExpectedFacts(CorrespondenceExceptionStoreTest.java:106)
at
com.google.common.truth.CorrespondenceExceptionStoreTest.describeAsAdditionalInfo_notEmpty(CorrespondenceExceptionStoreTest.java:79)
but it builds fine in my rawhide VM. But it's not obvious to me what
might be different or what's triggering this. Any help greatly appreciated.
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 https://www.nwra.com/
1 year, 6 months
Maven and Ant dependencies ported to Java 17
by Mikolaj Izdebski
Hello,
I've ported all my packages to be buildable with OpenJDK 17.
I have not pushed the changes to dist-git yet, but I will do it before
the end of the week.
I wanted to share common problems I encountered and solutions I came up with.
I hope that this will help others trying to port their packages.
Problem 1: Compiler source/target levels 1.6 are no longer supported
Solution: Bump source/target levels to 1.7 or 1.8
Packages affected:
- apache-commons-beanutils
- apache-commons-collections
- apache-commons-jxpath
- apache-commons-logging
- apache-commons-net
- apiguardian
- atinject
- bsf
- cglib
- java_cup
- jdom
- jdom2
- jsch
- junit
- jzlib
- maven-file-management
- maven-plugin-testing
- maven-shared-io
- munge-maven-plugin
- opentest4j
- osgi-annotation
- plexus-build-api
- qdox
- sisu-mojos
- xalan-j2
- xbean
- xml-commons-apis
Problem 2: Tests that use reflection fail with <<module java.base does
not "opens java.lang">> or similar error
Solution: Run tests with appropriate --add-opens parameter passed to JVM
Packages affected:
- easymock
- mockito
- xmvn
Problem 3: Code does not recognize Java bytecode version 61.0
Solution: Update to newer upstream version that supports newer Java bytecode.
Package affected:
- objectweb-asm
Problem 4: Code is compiled with -Werror passed to javac, but OpenJDK
17 introduces new warnings
Solution: Do not pass -Werror to Java compiler
Package affected:
- jakarta-mail
Problem 5: Wildcard imports are used in the code, but OpenJDK 17
introduces new classes that cause import ambiguity
Solution: Add explicit imports
Package affected:
- univocity-parsers
Packages that needed changes to make RPM Java packaging tooling to
work with OpenJDK 17:
- javapackages-bootstrap
- javapackages-tools
- maven
--
Mikolaj
1 year, 7 months
JDK 17 release package
by Devin Smith
Would it be possible to create the `java-17-openjdk` and related
packages given that JDK 17 is an LTS release?
Even though I can "install" against `java-17-openjdk`, I see that it
targets the rolling latest release `java-latest-openjdk`.
1 year, 7 months