Skip javadoc generation for test bundles - #2913
Closed
vogella wants to merge 2 commits into
Closed
Conversation
The javadoc profile the Jenkins job runs generates and jars API docs for every module, including the 23 test bundles whose docs are never published and whose jars the build throws away. Javadoc stays enabled for the published bundles, where doclint is the only check on HTML and syntax in doc comments that CI has. Same change as eclipse-platform/eclipse.platform.ui#4358. Pomless bundles get the property through build.properties, the five test bundles with an explicit pom.xml set it directly. Assisted-by: multiple AI agents and layers of automated tooling 🤖
Contributor
|
This pull request changes some projects for the first time in this development cycle. An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patchFurther information are available in Common Build Issues - Missing version increments. |
akurtakov
approved these changes
Sep 8, 2026
Contributor
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The
javadocprofile that the Jenkins job enables generates and jars API docs for every module in the reactor, including the 23 test bundles. Nobody publishes those docs and the Jenkinsfile archives only logs, so the jars are built and then thrown away.Javadoc stays enabled for the published bundles. Its doclint HTML and syntax checks are the only validation of doc comment markup in CI, since the GitHub Actions builds do not pass
-Pjavadocat all.Same change as eclipse-platform/eclipse.platform.ui#4358. Most test bundles here are pomless and get the property via
build.properties; the five with an explicitpom.xmlsetmaven.javadoc.skipdirectly, since thepom.model.property.mechanism only applies to pomless projects.