[
https://jira.codehaus.org/browse/MNG-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333069#comment-333069
]
Dennis Lundberg commented on MNG-5517:
--------------------------------------
As far as I understand it, version ranges are not part of the Semantic
Versioning specification at all. See http://semver.org/
The page you refer to contains conventions for the node-js project, which has
their own style for specifying version ranges.
> Supporting semver like syntax for <version> tag
> -----------------------------------------------
>
> Key: MNG-5517
> URL: https://jira.codehaus.org/browse/MNG-5517
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies, POM
> Reporter: Vijay Dharap
> Priority: Minor
>
> node js and its corresponding package manager - npm - follows semvar notation
> to depict the dependencies.
> The supported syntax variations for version specification can be seen here.
> https://github.com/isaacs/node-semver#ranges
> I find their syntax to be much more intuitive and subsequently user friendly
> than what is followed in current maven dependency <version> tag
> (http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-project-dependencies.html#pom-relationships-sect-version-ranges).
> Hope we can make the pom xml little more user friendly by adapting similar
> version specification syntax.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
