You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2010/05/26 17:59:37 UTC

[jira] Resolved: (CONFIGURATION-416) pom specifies incorrect groupId for commons dependencies

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

Sebb resolved CONFIGURATION-416.
--------------------------------

    Resolution: Invalid

Note that not all Commons components have been changed to use org.apache.commons. 

Many are still using commons-<component>, including Collections.

> pom specifies incorrect groupId for commons dependencies
> --------------------------------------------------------
>
>                 Key: CONFIGURATION-416
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-416
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.6
>            Reporter: Stanislav Ochotnicky
>            Priority: Minor
>
> pom.xml specifies commons depencencies as follows:
> <dependency>
>       <groupId>commons-collections</groupId>
>       <artifactId>commons-collections</artifactId>
>       <version>3.2.1</version>
> </dependency>
> Commons packages have been migrated to use correct groupId of org.apache.commons so these dependencies should be changed accordingly. We caught this when rebuilding commons packages using maven for Fedora rawhide and our build system was unable to find dependencies because of this.

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