Maven Eclipse Plugin
  1. Maven Eclipse Plugin
  2. MECLIPSE-380

dependencies in multi-module may projects require a 'mvn install' before using

    Details

    • Number of attachments :
      0

      Description

      The scenario is as follows:

      Parent Project P

      +-- Project A

      `- Project B

      B has a dependency on A (B requires A).

      A user with an empty local repository cannot checkout the whole project and
      run 'mvn eclipse:eclipse' due to unsatisfied dependencies. The build will
      fail in Project B because Project A is missing from the repository.

      A 'mvn install' has to be executed before (at least for Project A). But what
      if the project is in a state where it doesn't compile? It's not possible in
      this case for a new user to start developing with eclipse.

      See also http://www.nabble.com/maven-eclipse-plugin-with-multi-module-projects-to15222495s177.html

        Issue Links

          Activity

          Hide
          Martin Höller added a comment -

          Alfie Kirkpatrick did some research on this and posted the results here.

          It seems this issue is not related to MNG-2277 as Brian wrote, because MNG-2277 is closed already but this problem still exists with maven 2.0.9 and maven-eclipse-plugin 2.5.1.

          Show
          Martin Höller added a comment - Alfie Kirkpatrick did some research on this and posted the results here . It seems this issue is not related to MNG-2277 as Brian wrote, because MNG-2277 is closed already but this problem still exists with maven 2.0.9 and maven-eclipse-plugin 2.5.1.
          Hide
          Alfie Kirkpatrick added a comment -

          I think this issue can be closed as a duplicate of MNG-3283. This issue is not specifically related to the eclipse plugin, although that is the context we found it in.

          Note that you can work around this issue as siarhei suggested in the maven-users thread by running 'mvn process-classes eclipse:eclipse' because this goes further in the artifact resolution.

          Show
          Alfie Kirkpatrick added a comment - I think this issue can be closed as a duplicate of MNG-3283 . This issue is not specifically related to the eclipse plugin, although that is the context we found it in. Note that you can work around this issue as siarhei suggested in the maven-users thread by running 'mvn process-classes eclipse:eclipse' because this goes further in the artifact resolution.
          Hide
          Martin Höller added a comment -

          This issue is a duplicate of MNG-3283

          Show
          Martin Höller added a comment - This issue is a duplicate of MNG-3283
          Hide
          Martin Höller added a comment -

          not maven-eclipse-plugin specific

          Show
          Martin Höller added a comment - not maven-eclipse-plugin specific

            People

            • Assignee:
              Unassigned
              Reporter:
              Martin Höller
            • Votes:
              6 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: