paulrutter opened a new pull request, #593: URL: https://github.com/apache/felix-dev/pull/593
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:perform` runs (`performRelease=true`), every bundle now also gets a tag `<artifactId>-<version>` on the release commit, which is pushed to `origin`. It uses `exec-maven-plugin` calling `git tag` and `git push`, bound to `deploy` and 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 `deploy` creates no tags, a `deploy -DperformRelease=true` tags and pushes the bundles and not the parent. I could not run a real `release:perform`. A rerun after a failed perform fails on the existing tag, so remove the tags first. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
