Repository navigation
FELIX-6872 - Dependency Manager: tag every released bundle - #593
Merged
Merged
Conversation
The release plugin only makes one tag for the whole reactor (dependencymanager-parent-x.y.z). While performing a release, also tag each released bundle as <artifactId>-<version> on the release commit and push the tag, like the earlier releases did. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1 of 5 tasks
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.
The release plugin makes a single tag for the whole reactor (
dependencymanager-parent-x.y.z), so the 5.0.0 release has no tag per bundle, although the release notes say each bundle has its own tag and the earlier releases (e.g.org.apache.felix.dependencymanager-3.2.0) did.While
release:performruns (performRelease=true), every bundle now also gets a tag<artifactId>-<version>on the release commit, which is pushed toorigin. It usesexec-maven-plugincallinggit tagandgit push, bound todeployand skipped otherwise, so normal builds and deploys are unchanged. Only the five released bundles reference the plugin, so the parent and the integration test modules are not tagged.Tested in a scratch git repo with a bare remote: a plain
deploycreates no tags, adeploy -DperformRelease=truetags and pushes the bundles and not the parent. I could not run a realrelease:perform. A rerun after a failed perform fails on the existing tag, so remove the tags first.🤖 Generated with Claude Code