You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:46:26 UTC
[jira] [Closed] (MSHARED-139) Provide full information in the
attached POM to the artifact JAR
[ https://issues.apache.org/jira/browse/MSHARED-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MSHARED-139.
----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> Provide full information in the attached POM to the artifact JAR
> ----------------------------------------------------------------
>
> Key: MSHARED-139
> URL: https://issues.apache.org/jira/browse/MSHARED-139
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4
> Reporter: Mina R Waheeb
>
> In the current implementation of the JAR packaging, the POM file is copied as is to META-INF/maven/groupId/artifactId/pom.xml. The POM inheritance makes this file useless to identify this artifact outside the maven environment.
> For example:
> In the parent POM
> {code}
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.4</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> {code}
> in the child POM
> {code}
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> </dependency>
> </dependencies>
> {code}
> The child POM now declare dependency to junit:junit but there is no way to identify the version, scope or classifier and therefore i suggest attach a modified version of the POM to the artifact JAR file to provide the full information without inheritance or variables, so its become:
> {code}
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.4</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
> {code}
> Its very useful to make the artifact standalone and identifiable by any external systems.
> Thanks you.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)