You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mina R Waheeb (JIRA)" <ji...@codehaus.org> on 2009/12/19 09:38:56 UTC

[jira] Created: (MNG-4502) Provide full information in the attached POM to the artifact JAR

Provide full information in the attached POM to the artifact JAR
----------------------------------------------------------------

                 Key: MNG-4502
                 URL: http://jira.codehaus.org/browse/MNG-4502
             Project: Maven 2 & 3
          Issue Type: Improvement
          Components: POM
    Affects Versions: 2.2.0
            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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Moved: (MSHARED-139) Provide full information in the attached POM to the artifact JAR

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSHARED-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann moved MNG-4502 to MSHARED-139:
------------------------------------------------

           Complexity:   (was: Intermediate)
          Component/s:     (was: POM)
                       maven-archiver
    Affects Version/s:     (was: 2.2.0)
                       maven-archiver-2.4
                  Key: MSHARED-139  (was: MNG-4502)
              Project: Maven Shared Components  (was: Maven 2 & 3)

> Provide full information in the attached POM to the artifact JAR
> ----------------------------------------------------------------
>
>                 Key: MSHARED-139
>                 URL: http://jira.codehaus.org/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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira