3 Replies Latest reply on Mar 4, 2008 12:18 PM by adrian.brock

    Problem running tests in microcontainer/aop-mc-int

      I can't get the tests to run in aop-mc-int.

      Output using mvn -X test -Ptests-no-weave

      [DEBUG] Artifact not found - using stub model: Unable to determine the latest version
      
       org.apache.maven.plugins:maven-surefire-report-plugin:pom:LATEST
      
      
      [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-surefire-report-plugin:pom:LATEST
      [DEBUG] maven-surefire-report-plugin: using locally installed snapshot
      [DEBUG] Artifact not found - using stub model: Unable to determine the release version
      
       org.apache.maven.plugins:maven-surefire-report-plugin:pom:RELEASE
      
      
      [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-surefire-report-plugin:pom:RELEASE
      [INFO] ------------------------------------------------------------------------
      [ERROR] BUILD ERROR
      [INFO] ------------------------------------------------------------------------
      [INFO] The plugin 'org.apache.maven.plugins:maven-surefire-report-plugin' does not exist or no valid version could be found
      [INFO] ------------------------------------------------------------------------
      [DEBUG] Trace
      org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-surefire-report-plugin' does not exist or no valid version could be found
      


      I've got this workaround which is to disable the reference to the plugin

      Index: pom.xml
      ===================================================================
      --- pom.xml (revision 70351)
      +++ pom.xml (working copy)
      @@ -396,13 +396,13 @@
       </execution>
       </executions>
       </plugin>
      - <plugin>
      + <!--plugin>
       <artifactId>maven-surefire-report-plugin</artifactId>
       <configuration>
       <reportsDirectory>${project.build.directory}/surefire-reports/no-weave</reportsDirectory>
       <outputName>surefire-report-no-weave</outputName>
       </configuration>
      - </plugin>
      + </plugin-->
       </plugins>
       </build>
       </profile>
      @@ -665,4 +665,4 @@
       </build>
       </profile>
       </profiles>
      -</project>
      \ No newline at end of file
      +</project>
      


        • 1. Re: Problem running tests in microcontainer/aop-mc-int
          pgier

          I wasn't able to reproduce this locally. I did an svn update and a clean install of MC, and the tests ran fine (although there are a few test failures). I'm not sure why it can't find the surefire-report plugin for your build. You could try deleting just the surefire-report stuff from your local repo, and see if that helps.

          • 2. Re: Problem running tests in microcontainer/aop-mc-int

             

            "pgier" wrote:
            I wasn't able to reproduce this locally. I did an svn update and a clean install of MC, and the tests ran fine (although there are a few test failures). I'm not sure why it can't find the surefire-report plugin for your build. You could try deleting just the surefire-report stuff from your local repo, and see if that helps.


            Hmmm. Deleting all the surefire stuff from the local repostiory fixed that
            issue, so I can run the tests, but now they are all failing.
            A couple of hours ago I could run the tests with the plugin disabled???
            I've been working on other projects since then so no svn updates or changes
            (except possibly in the maven repository).

            I'll try blowing away my entire local repository. That usually fixes these issues,
            but it is very tiresome. Does maven use some kind of timestamp
            and its getting confused about what it needs to download?
            I know most of our checksums are broken in the repository so it can't use that. ;-)

            • 3. Re: Problem running tests in microcontainer/aop-mc-int

               

              "adrian@jboss.org" wrote:

              I'll try blowing away my entire local repository. That usually fixes these issues,


              Old faithful. If its not working, hit it with a hammer. ;-)
              Its working now.