You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Daniel Kulp (JIRA)" <ji...@codehaus.org> on 2007/02/12 16:23:21 UTC

[jira] Closed: (MRRESOURCES-7) Multiple entries are ignored

     [ http://jira.codehaus.org/browse/MRRESOURCES-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp closed MRRESOURCES-7.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0-alpha-2


This is fixed on trunk.   I deployed a new snapshot with this fixed last friday.  You can use the 1.0-alpha-2-SNAPSHOT version from the apache snapshot repository to test it.

(You're correct, this bug should have been reported in JIRA.   Thanks.)

Dan


> Multiple <resourceBundle> entries are ignored
> ---------------------------------------------
>
>                 Key: MRRESOURCES-7
>                 URL: http://jira.codehaus.org/browse/MRRESOURCES-7
>             Project: Maven 2.x Remote Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-1
>            Reporter: Al Maw
>         Assigned To: Daniel Kulp
>             Fix For: 1.0-alpha-2
>
>         Attachments: remote-resources-multiple-resourceBundle-issue.txt
>
>
> Configuration is as in the attachment.
> The key thing is that we're doing this:
> <resourceBundles>
>     <resourceBundle>org.apache:apache-jar-resource-bundle:1.0</resourceBundle>
>     <resourceBundle>org.apache:apache-incubator-disclaimer-resource-bundle:1.0</resourceBundle>
> </resourceBundles>
> We're finding that the first bundle is used just fine, but the second one is not.
> Expected result from the above config is that the JAR packaged for the project should have:
> META-INF/NOTICE.txt
> META-INF/LICENSE.txt
> META-INF/DISCLAIMER.txt
> However, the last of these (from apache-incubator-disclaimer-resource-bundle) is missing.
> It may be that this has already been fixed, but I couldn't find a closed bug for it and I'm sorry, but I haven't the time right now to build out of subversion and try the trunk version to find out. This should be an easy one to test, too. Even if it has been fixed in trunk, I reckon it should be noted here in JIRA so it makes the changelog. :-)
> Thanks -- Al

-- 
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