build: attach javadoc jar to release builds#6
Merged
Conversation
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
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.
Summary
Release builds did not generate javadoc jars because maven-javadoc-plugin in the root pluginManagement had no jar goal execution, while the core and toolkit modules only declare the plugin without executions. The super POM release-profile that used to handle this is no longer available in current Maven versions, so publishing to Maven Central fails validation during
mvn release:perform. Sources jars were already covered by the existing maven-source-plugin execution.Changes Made
attach-javadocsexecution (jargoal) to maven-javadoc-plugin in the rootpluginManagement, which the core and toolkit modules inheritTesting
mvn package -DskipTests -pl coreand confirmed thatjava-saml-core-*-javadoc.jaris generated alongside the sources jarAdditional Notes