Maven One Plugin (RETIRED)
  1. Maven One Plugin (RETIRED)
  2. MONE-2

Custom artifact handlers should be ignored

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: 1.0
    • Fix Version/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      If a custom packaging has a custom artifact handler, that handler (in particular, the file extension) should be ignored by the M2 --> M1 plugin.

      For example, if I create a packaging "foo" and use the artifact handler to declare that my packaging has the file extension "jar", then the plugin will currently create deploy files in the form "foos/a.jar". This is a corrupted repository from M1's point of view, which expects the packaging and the file extension to match in all cases.

      The workaround is to use M1's <jar> dependency field to override the calculated file name, but the real issue should also be fixed.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Matthew Beermann
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: