You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/05/01 19:43:12 UTC

[jira] Updated: (MNG-4654) Maven erroneously selects artifact handler contributed by extension plugin for use with project main artifact based on the handler's packaging rather than type

     [ http://jira.codehaus.org/browse/MNG-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MNG-4654:
-----------------------------------

    Description: 
This is mostly to track the result of [Compilation problem with Maven 3.0-beta-1|http://www.mail-archive.com/dev@maven.apache.org/msg84507.html] reported by Henrique Prange. In essence, given an artifact handler with
{code:xml}
<configuration>
  <type>woframework</type>
  <extension>jar</extension>
  <packaging>jar</packaging>
</configuration>
{code}
and a project with {{<packaging>woframework</packaging>}} using an extension plugin contributing the above artifact handler, Maven ignores the artifact handler because it tries to match {{project.packaging}} with {{artifactHandler.packaging}}. As a result, the project's main artifacts ends up being installed/deployed with the file extension "woframework" instead of "jar".

  was:
This is mostly to track the result of [Compilation problem with Maven 3.0-beta-1|http://www.mail-archive.com/dev@maven.apache.org/msg84507.html] reported by Henrique Prange. In essence, given an artifact handler with
{code:xml}
<configuration>
  <type>woframework</type>
  <extension>jar</extension>
  <packaging>jar</packaging>
</configuration>
{code}
and a project with {{<packaging>woframework</packaging>}} using an extension plugin contributing the above artifact handler, Maven ignores the artifact handler because it tries to match {{project.packaging}} with {{artifactHandler.packaging}}. 


> Maven erroneously selects artifact handler contributed by extension plugin for use with project main artifact based on the handler's packaging rather than type
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4654
>                 URL: http://jira.codehaus.org/browse/MNG-4654
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.2.1
>            Reporter: Benjamin Bentmann
>
> This is mostly to track the result of [Compilation problem with Maven 3.0-beta-1|http://www.mail-archive.com/dev@maven.apache.org/msg84507.html] reported by Henrique Prange. In essence, given an artifact handler with
> {code:xml}
> <configuration>
>   <type>woframework</type>
>   <extension>jar</extension>
>   <packaging>jar</packaging>
> </configuration>
> {code}
> and a project with {{<packaging>woframework</packaging>}} using an extension plugin contributing the above artifact handler, Maven ignores the artifact handler because it tries to match {{project.packaging}} with {{artifactHandler.packaging}}. As a result, the project's main artifacts ends up being installed/deployed with the file extension "woframework" instead of "jar".

-- 
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