commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COMMONSSITE-21) commons-parent-6 pom changes
Date Wed, 12 Dec 2007 18:30:43 GMT

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

Dennis Lundberg commented on COMMONSSITE-21:
--------------------------------------------

1 and 2 sound fine to me. Specifying the version of maven-release-plugin is definitely needed.

Regarding 3 I disagree. I think we should do it the other way around. If we are going to have
Maven 2 as the default build environment in Commons we should use standard Maven configuration
in commons-parent. When a component, for whatever reason, needs to deviate from the standard
way, we should add fixes or workarounds in *that* component. Using maven-remote-resources-plugin
is the way to go within the ASF for projects using Maven. If the data it uses (that goes into
the NOTICE file) isn't to our liking, then let's help fix the data.

> commons-parent-6 pom changes
> ----------------------------
>
>                 Key: COMMONSSITE-21
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-21
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            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.


Mime
View raw message