Maven
  1. Maven
  2. MNG-4490

Inconsistent handling of POMs

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0-alpha-5
    • Fix Version/s: 3.0-beta-3
    • Component/s: Plugins and Lifecycle
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      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.

        Activity

          People

          • Assignee:
            Benjamin Bentmann
            Reporter:
            Tamás Cservenák
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: