[
http://jira.codehaus.org/browse/MRRESOURCES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171533#action_171533
]
jieryn commented on MRRESOURCES-33:
-----------------------------------
My remote resources are outside the standard build, their unbundling is,
however, inside the main enterprise build (and is required to be, to be useful
at the enterprise level [20+ projects, 200+ modules)!
I'd really love to use ${project.version} however this variable does not get
interpolated the way I want it to when the pom is inherited. Instead of using
the ${project.version} for the master enterprise pom, where I am exploiting the
resource inside a <build> element, it is resolved at the lowest level. Thus,
the ${project.version} is resolved as the child's version which is not
necessarily the same as the one for the resource.
Please reconsider/reopen this. Thanks!
> 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
