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/09/17 23:54:33 UTC

[jira] Closed: (MNG-4490) Inconsistent handling of POMs

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

Benjamin Bentmann closed MNG-4490.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0-beta-3
         Assignee: Benjamin Bentmann

Fixed by [r988749|http://svn.apache.org/viewvc?view=revision&revision=988749], POMs are consequently treated as artifacts.

> Inconsistent handling of POMs
> -----------------------------
>
>                 Key: MNG-4490
>                 URL: http://jira.codehaus.org/browse/MNG-4490
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-alpha-5
>            Reporter: Tamás Cservenák
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-beta-3
>
>
> As we learned from discussion happened in issue MNG-4368, Maven3 -- depending on packaging ("pom" vs anything else)  -- handles the POM installation in different ways.
> When packaging is "pom", the POM is _handled as artifact_, and MNG-4368 (and any other future "optimization") interferes with it's installation. When packaging is not "pom", the POM is _handled as repository metadata in Maven3 internals.
> IMHO, the latter should be _always_ the case, regardless of the packaging type.

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