Fails to run build on Windows Server 2003

can you please retest this with the 2.3.1 snapshot? It can be tested from the ASF snapshot repository, or by building from:
http://svn.apache.org/repos/asf/maven/surefire/branches/surefire-2.3.x

I don't have the platform to test it on.

I added http://people.apache.org/repo/m2-snapshot-repository to my project.
Changed:
<artifactId>maven-surefire-plugin</artifactId>
<version>2.3.1-SNAPSHOT</version>

Now it does not run even Windows XP.
[INFO] [surefire:test]
[INFO] Surefire report directory: D:\devGwt\pyx4j\commons\target\surefire-report
s
[INFO] Building jar: D:\tmp\usr\vlads\surefirebooter23854.jar
java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/SurefireBooter
Exception in thread "main"
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Maven version: 2.0.5

This file was downloaded
maven-surefire-plugin-2.3.1-20070524.103536-2.jar

I've fixed that problem (sorry) - can you please retest?

Works fine on XP and Win server 2003
Thanks!

Build on Windows Server 2003 failed again!
---- build log —
Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/surefire/surefire/2.3.1-SNAPSHOT/surefire-2.3.1-20070606.164150-5.pom
Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-surefire-plugin/2.3.1-SNAPSHOT/maven-surefire-plugin-2.3.1-20070606.164150-5.jar
........
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
[INFO] ------------------------------------------------------------------------
---- build log —

May be the the problem is because I don't have any tests defined in a module But it works fine on WinXP
I removed the empty directories for test cases and the module build compleated.

but now next module fails that real has Unit tests.

C:\build\work\pyx4j-gwt\log4gwt>m2 -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building pyx4j-log4gwt
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\build\work\pyx4j-gwt\log4gwt\target\surefire-reports
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:48
0)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: There are
test failures.
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:425)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Jul 25 14:38:39 EDT 2007
[INFO] Final Memory: 5M/178M
[INFO] ------------------------------------------------------------------------
C:\build\work\pyx4j-gwt\log4gwt>

Maven version: 2.0.6

I was seeing the same behavior using an older version of the 1.5 jdk. After installing 1.5.0_12 the issue seems to be fixed.

This was my setup with the plugin failure.
Operating system : Windows 2003()
Java Home version :
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode)

Builder version :
Maven version: 2.0.7
Java version: 1.5.0_09
OS name: "windows 2003" version: "5.2" arch: "x86"

Here is my setup with it now working.
Operating system : Windows 2003()
Java Home version :
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)

Builder version :
Maven version: 2.0.7
Java version: 1.5.0_12
OS name: "windows 2003" version: "5.2" arch: "x86"

I'm noticing some seemingly significant issues between running Maven on Windows 2003 and other Windows versions (XP and Vista). I'm seeing a difference in the ordering of the classpath for compilation and test runs. Here's some log comparisons between a run of the exact same build using Maven 2.0.7, Sun JDK 1.5.0u12 on Windows Vista x86 and then again using Maven 2.0.7, Sun JDK 1.5.0u12 on Windows 2003.

Compilation Differences –

— Windows Vista
+++ Windows 2003
@@ -756,21 +756,21 @@
c:\temp\m2\repo\com\cerner\system\instrument\system-instrument\2.0\system-instrument-2.0.jar
c:\temp\m2\repo\com\cerner\system\system-i18n\2.0\system-i18n-2.0.jar
+ c:\temp\m2\repo\com\cerner\system\system-core\2.0\system-core-2.0.jar
c:\temp\m2\repo\com\cerner\system\system-jdbc\1.1.3\system-jdbc-1.1.3.jar
c:\temp\m2\repo\cerner\system-cache-jetstream\1.3.2\system-cache-jetstream-1.3.2.jar

• c:\temp\m2\repo\com\cerner\system\system-core\2.0\system-core-2.0.jar
  + c:\temp\m2\repo\cerner\dataobject-core\1.1.4\dataobject-core-1.1.4.jar
  c:\temp\m2\repo\cerner\dataaccess-core\1.1.2\dataaccess-core-1.1.2.jar
• c:\temp\m2\repo\cerner\dataobject-core\1.1.4\dataobject-core-1.1.4.jar
  c:\temp\m2\repo\com\cerner\mmf\mmf-dataaccess-jdbc\1.0-RC1\mmf-dataaccess-jdbc-1.0-RC1.jar
  c:\temp\m2\repo\com\cerner\mmf\xds\mmf-xds-person\1.0-SNAPSHOT\mmf-xds-person-1.0-SNAPSHOT.jar
  c:\temp\m2\repo\cerner\universal-id\1.3.0\universal-id-1.3.0.jar
• c:\temp\m2\repo\com\cerner\system\transaction\system-transaction\1.2\system-transaction-1.2.jar
  c:\temp\m2\repo\cerner\system-bootstrap\1.1.1\system-bootstrap-1.1.1.jar
  + c:\temp\m2\repo\com\cerner\system\transaction\system-transaction\1.2\system-transaction-1.2.jar
  c:\temp\m2\repo\cerner\system-concurrency\1.3\system-concurrency-1.3.jar
  c:\temp\m2\repo\cerner\system-management\1.1.1\system-management-1.1.1.jar
  c:\temp\m2\repo\com\cerner\mmf\mmf-factory\1.0-RC1\mmf-factory-1.0-RC1.jar
  c:\temp\m2\repo\cerner\system-cache\1.7.2\system-cache-1.7.2.jar
  c:\temp\m2\repo\cerner\system-registry\1.4.1\system-registry-1.4.1.jar
  c:\temp\m2\repo\cerner\system-event\1.0.3\system-event-1.0.3.jar
  c:\temp\m2\repo\cerner\system-urn\1.1.1\system-urn-1.1.1.jar]

Surefire launch –

— Windows Vista
+++ Windows 2003
@@ -2022 +2022 @@
-Forking command line: C:\Users\Public\jdk\sun\5_12\jre\bin\java -classpath c:\temp\m2\repo\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;c:\temp\m2\repo\junit\junit\3.8.1\junit-3.8.1.jar;c:\temp\m2\repo\org\apache\maven\surefire\surefire-api\2.3\surefire-api-2.3.jar;c:\temp\m2\repo\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;c:\temp\m2\repo\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;c:\temp\m2\repo\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;c:\temp\m2\repo\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;c:\temp\m2\repo\org\apache\maven\surefire\surefire-booter\2.3\surefire-booter-2.3.jar org.apache.maven.surefire.booter.SurefireBooter C:\Users\xxx\AppData\Local\Temp\surefire7271tmp C:\Users\xxx\AppData\Local\Temp\surefire7272tmp
+Forking command line: c:\install\jdk\sun\5_12\jre\bin\java -classpath c:\temp\m2\repo\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;c:\temp\m2\repo\junit\junit\3.8.1\junit-3.8.1.jar;c:\temp\m2\repo\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;c:\temp\m2\repo\org\apache\maven\surefire\surefire-api\2.3\surefire-api-2.3.jar;c:\temp\m2\repo\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;c:\temp\m2\repo\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;c:\temp\m2\repo\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;c:\temp\m2\repo\org\apache\maven\surefire\surefire-booter\2.3\surefire-booter-2.3.jar org.apache.maven.surefire.booter.SurefireBooter c:\temp\xxx\2\surefire34874tmp c:\temp\xxx\2\surefire34875tmp

Notice how the surefire-api JAR is in a different location this time.

re-closing - not enough info in original report, later commenter suggested it was a jdk bug, and ordering of classpath is addressed elsewhere

please open a new issue with a reproducible test case if you are still experiencing issues