You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2016/07/15 18:50:20 UTC
[jira] [Commented] (MNG-6064) Add "dev" string item into
ComparableVersion
[ https://issues.apache.org/jira/browse/MNG-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379902#comment-15379902 ]
Karl Heinz Marbaise commented on MNG-6064:
------------------------------------------
If I take a deeper look into the description I'm asking myself why do I need to create different version identifiers If don't have committed a change? If I don't have committed a change this means it is locally on my hard drive which means nobody else can use it...furthermore why does the kind version identifier influences if I create a tag or not? Apart from that if you like you can check if Maven can handle such versions via:
{code}
java -jar /usr/share/java/apache-maven-3.3.9/lib/maven-artifact-3.3.9.jar 0.1.0-milestone.1 0.1.0-milestone.1.dev.2+5612df0
Display parameters as parsed by Maven (in canonical form) and comparison result:
1. 0.1.0-milestone.1 == 0.1-milestone.1
0.1.0-milestone.1 < 0.1.0-milestone.1.dev.2+5612df0
2. 0.1.0-milestone.1.dev.2+5612df0 == 0.1-milestone.1.dev.2-+-5612-df
{code}
which shows correctly that the version {{0.1.0-milestone.1.dev.2+5612df0}} is identifier greater than the version {{0.1.0-milestone.1}}.
> Add "dev" string item into ComparableVersion
> --------------------------------------------
>
> Key: MNG-6064
> URL: https://issues.apache.org/jira/browse/MNG-6064
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 3.3.9
> Environment: Any operating Systems
> Reporter: Hui Wang
> Priority: Blocker
> Labels: maven
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> We're using a popular Gradle plugin "gradle-git" ( from Andrew Oberstar ) to implement Semantic Versioning with Continuous Deployment. There's a strategy supported by gradle-git that defines a "dev" stage when we have something uncommitted on a developer branch, which is very useful. Some examples to demonstrate the "dev" scenario can be found here: https://github.com/ajoberstar/gradle-git/wiki/Release%20Plugins#how-do-i-use-the-opinion-plugin
> However, current version of org.apache.maven.artifact.versioning.ComparableVersion does not support "dev" stage since there's no item "dev" in the field _QUALIFIERS of nested class StringItem. And since this is a private static final field, it is not able to be overwritten by inheritance. Can we add the "dev" item into _QUALIFIERS ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)