On Sat, Jan 1, 2011 at 12:22 AM, Steve Cohen <sco...@javactivity.org> wrote: > Well, all I can say is that I was doing approximately as you have described > and it didn't really work. > > I was using assembly:assembly (single for some reason failed to bring in > everything needed - perhaps the mistake was mine), I also used a separate > uber-project to do nothing but the assembly. But I noticed, once I started > actually doing the JUnit tests during the build run that they were being run
Running assembly:assembly is the bug that caused the goal "single" to be created. Because assembly is attached the lifecycle it incorrectly causes the entire lifecycle to be run twice. You will notice the same thing with surefire-report:report. Its a known problem that I think is being addressed in Maven 3.0. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
