[Claude] [TOOLCM-4386] Enable dual publishing to CodeArtifact#4
Open
sprout-autoagent wants to merge 1 commit into
Open
[Claude] [TOOLCM-4386] Enable dual publishing to CodeArtifact#4sprout-autoagent wants to merge 1 commit into
sprout-autoagent wants to merge 1 commit into
Conversation
Add maven-deploy-plugin configuration to publish artifacts to AWS CodeArtifact while maintaining existing Nexus deployment. Bump version from 4.0.6-dmevents to 4.1.0-dmevents. Because module POMs do not inherit from the root POM, the deploy plugin is added to each module individually. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Enable dual publishing to AWS CodeArtifact alongside the existing Nexus deployment for the twitter4j repository. This is part of the Phase 1 Nexus-to-CodeArtifact migration (TOOLCM-4349). The version is bumped from 4.0.6-dmevents to 4.1.0-dmevents to mark this configuration change. Because module POMs do not inherit from the root POM (no
<parent>element), the maven-deploy-plugin is added to each module individually rather than relying on parent inheritance.Change Summary
<version>from4.0.6-dmeventsto4.1.0-dmevents. Added a new top-level<build><plugins>section withmaven-deploy-pluginv3.1.4 configured with aus-deployexecution that targets the CodeArtifactaltDeploymentRepository. Added a<repositories>section with thesproutsocial-us-releasesrepository entry for dependency resolution. Existing Nexus<distributionManagement>block preserved unchanged.<version>to4.1.0-dmevents. Addedmaven-deploy-pluginwithus-deployexecution before</plugins>in<build>.<version>andtwitter4j-coredependency version to4.1.0-dmevents. Addedmaven-deploy-pluginwithus-deployexecution.<version>,twitter4j-coredependency, andtwitter4j-asyncdependency versions to4.1.0-dmevents. Addedmaven-deploy-pluginwithus-deployexecution.<version>andtwitter4j-coredependency version to4.1.0-dmevents. Addedmaven-deploy-pluginwithus-deployexecution.<version>andtwitter4j-coredependency version to4.1.0-dmevents. Addedmaven-deploy-pluginwithus-deployexecution.<version>andtwitter4j-coredependency version to4.1.0-dmevents. Addedmaven-deploy-pluginwithus-deployexecution.<version>and all 4 inter-module dependency versions (twitter4j-core,twitter4j-async,twitter4j-stream,twitter4j-media-support) to4.1.0-dmevents. Addedmaven-deploy-pluginwithus-deployexecution.Related Links