fix(ci): use excludeArtifacts to exclude tooling modules from Central bundle#49
Merged
pratyush618 merged 1 commit intomainfrom Mar 29, 2026
Merged
Conversation
… bundle The central-publishing-maven-plugin with <extensions>true</extensions> replaces the deploy lifecycle entirely, so maven.deploy.skip and central.publishing.skip have no effect — modules were still bundled without sources/javadoc/signatures, causing Central Portal rejection. Use the plugin's built-in excludeArtifacts parameter to properly exclude agenteval-intellij and agenteval-gradle-plugin from the publishing bundle. Remove ineffective skip properties (deploy, install, central.publishing.skip) from child modules, keeping only javadoc, source, and GPG skips which control their respective plugins directly.
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
1 participant
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
central-publishing-maven-pluginwith<extensions>true</extensions>replaces the deploy lifecycle entirely —maven.deploy.skipandcentral.publishing.skiphave no effect. Modules were still bundled without sources/javadoc/signatures, causing Central Portal to reject the deployment.excludeArtifactsparameter to properly excludeagenteval-intellijandagenteval-gradle-pluginfrom the publishing bundle.maven.javadoc.skip,maven.source.skip, andgpg.skipwhich control their respective plugins directly.Changes
pom.xml— add<excludeArtifacts>tocentral-publishing-maven-pluginconfig in release profileagenteval-intellij/pom.xml— remove ineffectivemaven.deploy.skip,maven.install.skip,central.publishing.skipagenteval-gradle-plugin/pom.xml— same cleanupTest plan
mvn verify -Bpasses — all 18 modules build successfully0.1.0tag after merge