Closed KonradHoeffner closed 3 years ago
I think this was the jacoco plugin. I removed it in the last bug fix release. Building works fine for me on adoptopenjdk16.
Running mvn package
of the newest commit 30c7484e215a8d24b56d8e1c47ee3969f0c4970b from May 11 still fails, but with a different error, so I guess that one is resolved and I will open a new one for the other error.
Yes, that other error was just because JAVA_HOME was not set, mvn package
works fine now.
javadoc, which relies on the correct JAVA_HOME env was previously disabled for reasons I do not remember. I enabled it for the last release, which is probably why you just encountered this error.
This is unfortunate, because e.g. Arch Linux doesn't seem to set JAVA_HOME by default when installing Java using the package manager.
Then java, javac and javadoc are on the path but still aren't found by maven-javadoc-plugin.
However you can fix this by setting the javadocExecutable
in pom.xml like so:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<javadocExecutable>${java.home}/bin/javadoc</javadocExecutable>
</configuration>
</plugin>
See https://stackoverflow.com/questions/13961615/unable-to-find-javadoc-command-maven.
Running
mvn package
on the newest master branch produces dozens of exceptions like the following. The most important part seems to bejava.lang.IllegalArgumentException: Unsupported class file major version 59
. I guess that there is some problem with newer Java versions. I'm using openjdk 15.0.2 2021-01-19.