You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jieryn (JIRA)" <ji...@codehaus.org> on 2009/03/27 13:45:12 UTC

[jira] Commented: (MRRESOURCES-33) Have to specifiy the version number twice in a pom

    [ 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