Ken Glad to hear you have it fixed.
It makes sense now, our project had to use manifest jars because we had so many third party libraries required for unit testing that the classpath got too long for the windows command line. They basically contain (for us) a manifest pointing to the other jars for the sole purpose of shortening that command line. I guess the surefire plugin had the same problem and there is something about how they are specified in the manifest which doesn't work on your filesystem, http://maven.apache.org/plugins/maven-surefire-plugin/examples/class-loading.html Thanks for posting the solution Brian On 28 September 2010 18:47, Kenneth McDonald < [email protected]> wrote: > Posting this in hopes it will help others. First, I'd like to heartily > thank everyone who gave of their time with helping me in this problem. I > learned a log about maven (more than I really want to :-) but it's good for > future jobs), and I wouldn't have found the solution on my own without a > _lot_ more time. > > Basically, a couple of people sent me pom files which worked for them, but > which didn't work for me. I don't know why, this is still a mystery. What > did work was the following highlighted line: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-surefire-plugin</artifactId> > <version>2.6</version> > <configuration> > <useManifestOnlyJar>false</useManifestOnlyJar> <---- > <includes> > <include>**/*Test.*</include> > <include>**/*Suite.*</include> > </includes> > </configuration> > </plugin> > > I'm going to have to dig into the Maven documentation and refresh my memory > of manifests (its been _years_ since I've used Java) to figure out exactly > what is going on, but once I added this, my tests ran smoothly. (And I am > happy to say, all are still OK :-) ). > > Again, many thanks to all, > Ken McDonald
