[
http://jira.codehaus.org/browse/MNG-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202357#action_202357
]
Benjamin Bentmann commented on MNG-4490:
----------------------------------------
For the record, this is not specific to Maven 3 but applies equally to Maven 2.
> Maven3 is inconsistent about handling 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
>
> 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
