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

M1 deploy blows away local repository metadata

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Blocker Blocker
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: None
    • Labels:
      None
    • Number of attachments :
      1

      Description

      Steps to reproduce:

      1) Bind maven-one-plugin:deploy-maven-one-repository to the "deploy" phase (and add suitable configuration).
      2) Run "mvn deploy" on a project
      3) After the deploy finishes, look at maven-metadata.xml for the project in the local repository.
      4) Note that the file has been overwritten with invalid contents.

      In particular, the local repository metadata has been overwritten by the file legacy_repo/$

      {groupId}

      /poms/maven-metadata.xml. Unfortunately, because of the way M1 repositories are structured, this file contains version numbers for all artifacts in the group. I'll attach mine in a moment as an example.

      This effectively corrupts the local repository. Subsequent builds that depend on the affected project will fail because they're looking for phantom version numbers that don't exist.

      Note: we recently switched to the WebDAV wagon for deployment, and this bug seemed to show up at about the same time. The two could be related, or it could just be a red herring...

        Activity

        No changes have yet been made on this issue.

          People

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

            Dates

            • Created:
              Updated: