Uploaded image for project: 'Maven Eclipse Plugin (RETIRED)'
  1. Maven Eclipse Plugin (RETIRED)
  2. MECLIPSE-388

Correct classpath ordering in .classpath

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Currently plugin sorts artifacts on its own (alphabetic order???) because the order of dependencies that comes from maven is not reliable (random?). This breaks tests that use JBoss Embedded which works under maven surefire plugin because it still puts dependencies that came first at the beginning of the classpath). Apparently not all classpath elements are put in random order. At least I get the first ones listed in dependencies also first in the classpath (can be seen as ${surefire.test.class.path} and in target/surefire-reports/TEST-TestSuite.xml).

      While there is not much we can do for maven eclipse plugin a solution is on the way: MNG-1412. When maven 2.0.9 is released maven eclipse plugin can revert back to the default classpath order.

      Can we somehow schedule this?

      Another question: is there anyway to put certain dependencies in the first place except for renaming them so that alphabetic order does the job?

      Attachments

        1. ideal.classpath
          1 kB
          Jean-Noel Rouvignac
        2. MECLIPSE-388.patch
          2 kB
          David J. M. Karlsen
        3. MECLIPSE-388.patch
          2 kB
          David J. M. Karlsen
        4. MECLIPSE-388-it-test.patch
          8 kB
          David J. M. Karlsen
        5. Test.zip
          2 kB
          Jean-Noel Rouvignac

        Issue Links

        is duplicated by

        Bug - A problem which impairs or prevents the functions of the product. MECLIPSE-665 wrong classpath order generated in .classpath file for transitive dependencies

        • Major - Major loss of function.
        • Closed
        is related to

        Bug - A problem which impairs or prevents the functions of the product. MECLIPSE-705 Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.

        • Critical - Crashes, loss of data, severe memory leak.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MNG-1412 dependency sorting in classpath

        • Major - Major loss of function.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. MNG-3118 Test-classes should come before classes in the classpath

        • Major - Major loss of function.
        • Closed
        relates to

        Improvement - An improvement or enhancement to an existing feature or task. MECLIPSE-318 test classes and resources need to be first in .classpath file

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            baerrach Barrie Treloar
            svadu Siarhei Dudzin
            Votes:
            11 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment