www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-4522) Nexus should check that pom metatdata agrees with the pom in the associated jar
Date Wed, 07 Mar 2012 14:14:59 GMT

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

Brian Demers closed INFRA-4522.

    Resolution: Unresolved

Feature request moved to:
> Nexus should check that pom metatdata agrees with the pom in the associated jar
> -------------------------------------------------------------------------------
>                 Key: INFRA-4522
>                 URL: https://issues.apache.org/jira/browse/INFRA-4522
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Sebb
>            Assignee: Brian Demers
> Where a pom describes a jar that contains a pom, Nexus should check that the metadata
> This would have prevented some projects from releasing renamed jars using incorrect Maven
> For example, the external metadata:
> <dependency>
>   <groupId>org.apache.solr</groupId>
>   <artifactId>solr-commons-csv</artifactId>
>   <version>3.5.0</version>
> </dependency>
> actually refers to 
>   <groupId>org.apache.commons</groupId>
>   <artifactId>commons-csv</artifactId>
>   <version>1.0-SNAPSHOT</version>
> Ideally, there should also be some check of the package names for jars that don't have
embedded POMs, as for example:
> <dependency>
>   <groupId>org.apache.solr</groupId>
>   <artifactId>solr-carrot2-core</artifactId>
>   <version>3.5.0</version>
> </dependency>
> which uses the org.carrot2 package name space - which is unlikely to be an ASF package
> However, this is tricky to do accurately, so should probably only generate a warning.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message