[ 
http://issues.ops4j.org/browse/PAXURL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11803#action_11803
 ] 

Toni Menzel commented on PAXURL-1:
----------------------------------

actually i like this but real regular expressions are conflicting the the 
current segment based interpretation.
Integration regex would break backwards compatibility or make defining versions 
a real mess. (how do you distinglish regex versions from segment based version 
notations ?)
Another possibility would be to introduce special chars into the existing 
segment scheme. So that you can place an astersik (*) between segments, saying 
exactly what didiers suggestion was about.
Example: 1.* to get the highest 1 version.
@alin, as mantainer of pax url, wdyt ?


> Support regexp expressions for version resolution in mvn: handler
> -----------------------------------------------------------------
>
>                 Key: PAXURL-1
>                 URL: http://issues.ops4j.org/browse/PAXURL-1
>             Project: Pax URL
>          Issue Type: New Feature
>          Components: mvn
>            Reporter: Alin Dreghiciu
>            Assignee: Toni Menzel
>            Priority: Minor
>
> On suggestion of Didier Donsez:
> Maven 2 handler (mvn:)  should add support for resolving the version of an 
> artifact based on a regexp expression, so could be used as:
> mvn:commons-logging/commons-logging/1\..*
> that would be resolvd to the highest version that matched the regexp 
> expression. In the above exemple will be matched to the highest version that 
> starts with 1. (e.g 1.1)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to