-
Notifications
You must be signed in to change notification settings - Fork 323
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
Allow skipping version manipulation to avoid getting the version mangled #314
Comments
Manage to work around this by using a different property to inject that is not mangled by jdeb. I'm using |
The mangling is clearly wrong in this case, the end of the |
We should have a testcase that covers all those conversions. Maybe it would be good to start with a table of how conversions should look like. |
I just observed the following in my build which seems to be related to this issue: |
I think we first need to define all the expectations in the tests. Otherwise I don't see a chance of fixing this. So if you could contribute your expectations here
that would be great. |
I don't have much time right now, so I just put the assertions below here, I hope you apologize for not making a proper PR. In testVersionConversion:
In testVersionConversionWithTemplate:
|
The current implementation in Utils. convert a "java" version into a "debian" version. Trying to handle alhpa, beta, release. But It doesn't cover all the scenario and we should have an option to completely skip the version mangling an keep the version of the package.
e.g.: I'm using this version
3.7.1~dev24+g1b4b40e
and it get transformed into3.7.1~dev24+g1b4~b40e
.A simple option to skip the version mangling should be added to let the users manage it own version semantic.
The text was updated successfully, but these errors were encountered: