-
Notifications
You must be signed in to change notification settings - Fork 32
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
version parameter is ignored on SNAPSHOT builds #52
Comments
Thanks for the report. I didn't use this plugin for a while, so I may have missed a point. Taking a look at the documentation (good I did that 😁 ) there is the following behavior (or at least, there should be):
So I guess, in your case, you should be able to use |
Sorry for the late response and thank you for your feedback. You are right, the implementation correctly follows the documentation. But it is quite tedious in Maven to set So another suggestion would be to introduce a If that sounds like a good idea, I would create a pull request for it. |
Yes, that sounds like a good idea. |
Ok, I will see when I find some time. First I have to go on vacation for the next two weeks. |
Hi,
is there a good reason that in the case of a snapshot build, an explicitly defined version string via the
<version>
parameter is ignored?In our case, the Maven version contains a hyphen (i.e. 2021-1.0.1-SNAPSHOT or 2021-1.0.1 for the release).
The extra hyphen confuses
zypper
and a snapshot RPM likefoo-2021-1.0.1-0.202101020304.noarch.rpm
cannot be removed via:zypper remove foo
->Error: RPM failed: error: package foo-2021-1.0.1-0.202101020304.noarch is not installed
.So we use something like 2021_1.0.1 derived from the project version and use it with the
<version>
parameter tag for our release packages, but always have to remove the shapshot RPMs withrpm -e ...
by hand.I have already created a patch to try this out, but would need to adjust the tests to submit a PR.
Additionally, a new parameter could be introduced to switch between old and new behavior if needed.
Already thanks for feedback and all the great work that went into this plugin.
The text was updated successfully, but these errors were encountered: