[
http://jira.codehaus.org/browse/MRRESOURCES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171481#action_171481
]
Brett Porter commented on MRRESOURCES-33:
-----------------------------------------
... but if you do, the correct way is to use ${project.version}. The resource
bundle shouldn't be a dependency of the project.
As for wanting to have <dependency> type processing or at least classifier
support - please make a separate more specific request. I don't see the need
for a classifier bundle myself.
> Have to specifiy the version number twice in a pom
> --------------------------------------------------
>
> Key: MRRESOURCES-33
> URL: http://jira.codehaus.org/browse/MRRESOURCES-33
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Improvement
> Affects Versions: 1.0-beta-2
> Environment: mvn 2.0.5
> Reporter: EJ Ciramella
>
> Currently, you have to specify the version number twice in a pom if you need
> to unpack a dependency.
> <resourceBundles>
> <resourceBundle>groupId:artifactId:version</resourceBundle>
> </resourceBundles>
> It'd be nice if you could just rely on the dependency tags for this instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
