You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "EJ Ciramella (JIRA)" <ji...@codehaus.org> on 2008/03/15 01:32:29 UTC
[jira] Created: (MRRESOURCES-33) Have to specifiy the version
number twice in a pom
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
[jira] Commented: (MRRESOURCES-33) Have to specifiy the version
number twice in a pom
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRRESOURCES-33) Have to specifiy the version
number twice in a pom
Posted by "jieryn (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRRESOURCES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171191#action_171191 ]
jieryn commented on MRRESOURCES-33:
-----------------------------------
This is rather critical, as the maven-release-plugin does not update the hard coded values here in the version. Which means that if you use resourceBundles in the same reactor as where they are created, then a release:prepare will miss them and the build will become unstable (provided you use the resources in an attached <build> segment, or something else I haven't thought of).
Also, the resourceBundle doesn't take into account any possible classifiers. Please, MRR, just use standard <dependency> type processing. I realize this would break backwards compatibility, but this resourceBundle style is just broken beyond fixing. If we used the same notation as Maven dependency specification we could piggy back on core Maven code, presumably well tested core code. :-)
http://maven.apache.org/pom.html#Maven_Coordinates
> 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
[jira] Closed: (MRRESOURCES-33) Have to specifiy the version number
twice in a pom
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRRESOURCES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MRRESOURCES-33.
------------------------------------
Resolution: Won't Fix
Don't put remote resources in a standard build. They should be separated as the intent is that they are shared amongst other projects.
> 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
[jira] Commented: (MRRESOURCES-33) Have to specifiy the version
number twice in a pom
Posted by "jieryn (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRRESOURCES-33) Have to specifiy the version
number twice in a pom
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRRESOURCES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171542#action_171542 ]
Brett Porter commented on MRRESOURCES-33:
-----------------------------------------
in this case, please consider a different property that you just need to set once (see ${mavenVersion} in the Maven POM).
The release plugin (and to some extent the reactor) is not designed to cross version boundaries in this way.
> 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