Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0 (2.2 plugin)
    • Fix Version/s: 2.3.1
    • Component/s: JUnit 3.x support
    • Labels:
      None
    • Environment:
      maven2.0.4, sun-jdk-1.5.0.09, maven-surefire-plugin 2.2, surefire 2.0, gentoo linux x86
    • Flags:
      Patch

      Description

      Surefire incorrectly interprets classpath ordering.
      Steps to reproduce:
      1. unzip my-app.zip - it's a simple mvn project created with
      mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app
      and lightly patched
      2. mvn test
      in my case, it prints out
      jar:file:/home/vyzivus/.m2/repository/jxta/jxta/2.0/jxta-2.0.jar!/log4j.properties
      jar:file:/home/vyzivus/.m2/repository/jxta/jxta/2.0/jxta-2.0.jar!/log4j.properties
      which is incorrect. log4j.properties is located both in jxta.jar and src/test/resources, but I think that src/test/resources takes precedence over jxta. This ordering is set correctly in surefire36745tmp file I think, but surefire seems to ignore the ordering.

        Attachments

        1. SUREFIRE61-surefire-booter-r558713.patch
          2 kB
          Paul Gier
        2. output.log
          22 kB
        3. SUREFIRE61_barrettas_surefire_surefire-booter_for_rev_489098.patch
          2 kB
          Barrett Snyder
        4. my-app.zip
          5 kB
          Martin Vysny

          Issue Links

            Activity

              People

              • Assignee:
                brettporter Brett Porter
                Reporter:
                vyzivus Martin Vysny
              • Votes:
                5 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: