[
https://jira.codehaus.org/browse/MRRESOURCES-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277893#comment-277893
]
Robert Scholte commented on MRRESOURCES-55:
-------------------------------------------
Any reason why you decided to choose for {{VersionRange.createFromVersionSpec(
version )}}?
This would mean that you can specify version ranges, which doesn't seem right
to me.
> Support groupId:artifactId:version:type and
> groupId:artifactId:version:type:classifier as resource bundle references
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MRRESOURCES-55
> URL: https://jira.codehaus.org/browse/MRRESOURCES-55
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: New Feature
> Affects Versions: 1.2
> Reporter: Andrew Phillips
> Attachments: MRRESOURCES-55-preserve-original-codepath-patch.txt,
> MRRESOURCES-55-remote-resources-patch.txt
>
>
> Currently, the RR plugin only support groupId:artifactId:version as an
> identifier for a remote bundle. However, there are quite a few use cases
> (e.g. platform-specific bundles) where it would be very useful to be able to
> identify bundles additionally by classifier. The current workaround we use -
> different versions - works, but isn't particularly elegant or semantically
> accurate.
> The proposal therefore is to also allow identifiers of the type
> groupId:artifactId:version:type:classifier
> As Brett pointed out in an IRC chat, this automatically adds the type to the
> identifier as well. One could ignore it or enforce 'jar' (the current
> default), but on the other hand there seems to be no reason *not* to allow
> types such as 'zip', or even 'war' or 'ear'. Only 'pom' doesn't make much
> sense.
> Two potential implementations, with tests, are attached.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
