[ 
https://issues.apache.org/jira/browse/COMMONSSITE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Niall Pemberton updated COMMONSSITE-21:
---------------------------------------

    Attachment: COMMONSSITE-21-commons-parent-pom-v1.patch

Attaching a patch for the commons-parent pom which does the following:

1) Configure the maven-release-plugin in the "rc" profile with an "arguments" 
value of "-Prc" 
2) Configure the maven-release-plugin in the "release" profile with an 
"arguments" value of "-Prelease"

Trying to release commons-skin I found that the deploy step was not picking up 
the the repository from the specified profile. So for example using:
    mvn -Prc perform:release
ignored the configured repository for the "rc" profile and tried to deploy to 
the "dummy" repository specified in commons-parent pom.

Without actually releasing something I can't test whether this proposed 
solution will work - but the commons logging pom has a similar configuration 
for that plugin (but in the build profile)
   http://svn.apache.org/repos/asf/commons/proper/logging/trunk/pom.xml

3) Remove the maven-remote-resources-plugin (from "rc" and "release" profiles)
Currently this plugin is automatically adding "License" and "Notice" files 
(without the .txt extension) to the meta-inf directory in jars - since all our 
components already have NOTICE.txt and LICENSE.txt files which are configured 
as "resources" this causes duplicate license/notice files to be added to the 
jar. Also the generated notice file adds entries for dependencies - which if 
they don't have appropriate organization/license info sepcified in their poms 
says "developed by an
unknown organization" - this doesn't look too good, especially when the 
dependencies are Apache projects (examples BeanUtils 1.7.0 and Jakarta ORO)

> commons-parent-6 pom changes
> ----------------------------
>
>                 Key: COMMONSSITE-21
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-21
>             Project: Commons All
>          Issue Type: Improvement
>            Reporter: Niall Pemberton
>         Attachments: COMMONSSITE-21-commons-parent-pom-v1.patch
>
>
> Opening this ticket to discuss changes for Version 6 of the commons-parent 
> pom.
> See thread: http://tinyurl.com/39eo9z for related discussion/issues

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to