maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRRESOURCES-31) Add an "alternative" apache-jar-resource-bundle
Date Tue, 08 Jan 2008 03:00:57 GMT

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

Niall Pemberton updated MRRESOURCES-31:
---------------------------------------

    Attachment: NOTICE.txt.vm
                LICENSE.txt.vm
                pom.xml

Sorry, the svn client I use (TortoiseSVN) doesn't create patches properly when new directories
are added - so I'm just attaching the three files. Directory structure is the same as apache-jar-resource-bundle.

> Add an "alternative" apache-jar-resource-bundle
> -----------------------------------------------
>
>                 Key: MRRESOURCES-31
>                 URL: http://jira.codehaus.org/browse/MRRESOURCES-31
>             Project: Maven 2.x Remote Resources Plugin
>          Issue Type: Improvement
>            Reporter: Niall Pemberton
>         Attachments: LICENSE.txt.vm, NOTICE.txt.vm, pom.xml
>
>
> I propose adding an "alternative" apache-jar-resource-bundle (perhaps called "apache-jar-resource-bundle-alt"?)
which is a copy of the existing apache-jar-resource-bundle[1] except that the 
>    LICENSE.vm is renamed to LICENSE.txt.vm
>    NOTICE.vm is renamed to NOTICE.txt.vm
> This will create files named LICENSE.txt and NOTICE.txt rather than LICENSE and NOTICE.
> The ASF policy[2] on the naming of these files says:
>  -  Can the LICENSE and NOTICE files be called LICENSE.txt and NOTICE.txt?
>  - This is permitted. However the preference is that the files be called LICENSE and
NOTICE.
> Many projects use ".txt" extensions as its more friendly to windows users and since the
policy says its permitted then IMO it would be good to support projects which chose to use
that naming convention with a standard resource bundle.
> This has come out of a discussion at Apache Commons [3] and a bundle such as this would
allow that project (with 34 diffferent components, each with a copy of NOTICE.txt and LICENSE.txt)
to be able to easily migrate to using the remote-resources-plugin with minimal effort. Currently,
configuring the remote-resources-plugin in Commons's parent pom causes duplicate Notice and
License files (i.e. versions with and without the .txt extension).
> Apologies if this is filed in the wrong place - but theres no issue tracking link in
the pom for apache-jar-resource-bundle to indicate where issues should be filed.
> [1] http://svn.apache.org/repos/asf/maven/resources/trunk/apache-jar-resource-bundle/
> [2] http://apache.org/dev/apply-license.html#license-file-name
> [3] http://issues.apache.org/jira/browse/COMMONSSITE-21

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

        

Mime
View raw message