-
Notifications
You must be signed in to change notification settings - Fork 267
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
set-scm-tag functionality needed for Subversion #342
Labels
Milestone
Comments
Partial support is already included: see I'm working on an enhancement to that so that it'll also be possible to define scm elements which don't currently exist in the POM. |
andrzejj0
added a commit
to andrzejj0/versions-maven-plugin
that referenced
this issue
Sep 16, 2022
andrzejj0
added a commit
to andrzejj0/versions-maven-plugin
that referenced
this issue
Sep 16, 2022
andrzejj0
added a commit
to andrzejj0/versions-maven-plugin
that referenced
this issue
Sep 16, 2022
slawekjaranowski
pushed a commit
that referenced
this issue
Sep 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In working w/scripting some release:prepare -like functionality for RCP-based applications (Maven's release plugin doesn't directly support the manifest-based RCP builds, Tycho plugin doesn't support the tagging), I've come across the initial enhancement request at:
#182
...but in reading the comments it appears the Git-only support was implemented via the set-scm-tag goal (never found the discussed documentation that would explain this was Git-only support).
Here's my script (running in Jenkins v2.160 Windows Batch Command):
My attempts at utilizing set-scm-tag on a Subversion-supported project results in the following error/stacktrace:
Subversion support could use 'newTag' to change the , , and elements all at once, or new args could be added for each if they needed to be changed individually (we keep the 3 matching all the time, not sure if others do the same).
This would really be helpful when trying to configure RCP-based/Subversion-supported projects for CI/CD processes.
The text was updated successfully, but these errors were encountered: