Adapt to changed output directory in maven-javadoc-plugin 3.10.0 #1402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Build artifacts look good. |
|
Something similar might be required for other doc bundles as well! |
I thought that as well, but at least the tests for the other doc bundles didn't report a problem. Not sure if this is false positive or if PDE is different. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Probably as part of apache/maven-javadoc-plugin#204, the default output directory of the
maven-javadoc-pluginchanged when updating themaven-javadoc-pluginfrom3.8.0to3.10.0. This adapts the doc-bundle build accordingly.In a local test the missing
reference/apifolder was generated in the project as expected, but the built jar still didn't contain it. So maybe more adaption is necessary.Hopefully fixes #1392