Set maven.compiler flags explicitly #13710
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ran into another issue while doing 1.2.0 Release.
What was the error?
The error came on running
release:prepare
. There were a bunch of errors like the following. These were coming from the.maven-javadoc-plugin
, which for some reason was using source Java version as 7:Why is the Javadoc Plugin using source version as 7
This is because
maven-javadoc-plugin
is apparently now using the "release" flag for JDK 9 and above. This flag was introduced inmaven-javadoc-plugin:3.1.0
(ref). This is by default set tomaven.compiler.release
, which is set to 7 in Apache's POM (ref)Why didn't this happen with Pinot 1.1.0 Release?
This is likely because of a version upgrade of
maven-javadoc-plugin
.How do we know this change actually fixes the issue?
Verified by cloning the
release-1.2.0-rc
tag, and running the following. The command fails but when I use the patch in this PR, it works: