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 22:16:43 GMT

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

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

I have studied the current svn trunk version of project.xml and pom.xml files for all commons
projects. For multiprojects like jelly and jci I just looked at the component parent.

All project.xml files include an <organization> element. All pom.xml files inherit from
commons-parent-5, which inherits from apache-parent-4, which includes an <organization>
element. So any commons release from here on *will* have a proper <organization> element.

Looking at dependencies on other commons components in all current svn trunk project.xml files
I found that the following components lacks an <organization> element in their poms
in the central repository. Each component is a dependency in only one other component:
- pool-1.1
- discovery-0.2
- digester-1.4.1
- codec-1.2

Then we have beanutils-1.7, which is a dependency in many other common components. Something
has gone wrong when this was deployed to the repository. The M1 repo is missing the pom all
together and the M2 repo has a pom that cannot stem from the original project.xml in the svn
tag. This is something that can probably fixed in the repository because it is not the correct
pom that has been deployed. If no one objects I will open a JIRA for this over at http://jira.codehaus.org/browse/MEV
to see if we can get it fixed.

As you can see there are very few of our own dependencies that have bad meta data in the central
repository, with beanutils-1.7 being the exception to the rule here. So I believe that using
maven-remote-resources-plugin will work for most commons components when it is time to release
its next version.

> 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