Uploaded image for project: 'Maven Release Plugin'
  1. Maven Release Plugin
  2. MRELEASE-326

Doens't resolve multiproject dependencies properly

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 2.0-beta-7
    • None
    • prepare
    • None
    • Windows, JDK 1.6, Maven 2.08

    Description

      I'd try to make a release:prepare from a multiproject:

      A (Multiproject POM)
      B (Core Interfaces)
      C (Component)
      D (Core Impl)
      E (Standalone Client)
      F (EJB)
      G (Client)

      A is the parent project and contains the other project from B to G. Following dependencies are defined : G -> F -> D -> B -> A

      However, when it comes to build the Artifact G, the release plugin aborts, because of missing Artifact F. But it's part of the Multiproject and was just build before. The release plugin checks the remote repository for an existing version. Which is non-sense, since I'm actually try to buld it right now...

      Since the release plugin has already changed the pom from Snapshot to stable version labels. I can now do "mvn install" and the missing Artefact will be installed. And the second run of mvn release:prepare will succeed! Though, I don't like this workaround and hope this can be fixed.

      Thanks

      Kuno

      Attachments

        1. Stacktrace_release-plugin.txt
          11 kB
          Kuno Baeriswyl

        Issue Links

          Activity

            People

              olamy Olivier Lamy
              qnob Kuno Baeriswyl
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: