-
Notifications
You must be signed in to change notification settings - Fork 1
build: remove TestBench dependencies from the published POM #168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: FlowingCode/CommonsDemo
Length of output: 5070
🏁 Script executed:
Repository: FlowingCode/CommonsDemo
Length of output: 12997
🏁 Script executed:
Repository: FlowingCode/CommonsDemo
Length of output: 8958
🏁 Script executed:
Repository: FlowingCode/CommonsDemo
Length of output: 312
🏁 Script executed:
Repository: FlowingCode/CommonsDemo
Length of output: 1222
🏁 Script executed:
Repository: FlowingCode/CommonsDemo
Length of output: 4599
Use an immutable
dev-nuke-maven-pluginversion for release builds.The
dev-nukegoal runs duringprocess-resources, removes<?dev-only?>nodes, writespom-transformed.xml, and sets it as the Maven project file. Thereleaseprofile publishes throughcentral-publishing-maven-plugin, so this transformed POM can be published. The configured snapshot repository enables snapshot resolution, and1.0.0-SNAPSHOTresolves to mutable timestamped artifacts. A later build of the same source revision can therefore publish a different POM. Release the plugin and use its immutable version before publishing.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to merge this one first, in order to validate the snapshot release pipeline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@javier-godoy, understood. Keep1.0.0-SNAPSHOTin this PR to validate the snapshot release pipeline.The immutable plugin version change can follow after that validation. Would you like me to open a GitHub issue for the follow-up?
You are interacting with an AI system.