On Thu, Apr 8, 2010 at 4:46 PM, Benjamin Bentmann <benjamin.bentm...@udo.edu > wrote:
> Laird Nelson wrote: > > But in surefire with<forkMode>always</forkMode>, the classpath is actually >> a surefirebooter.jar located in $TEMP with a big ol' Manifest Class-Path: >> entry. >> > > [0] describes some options to control how the test class path is created. I > would expect that one of these solves your problem. > Sure; thanks; I'm actually not objecting to surefire's behavior at all. A manifest-only jar is just fine with me, but Glassfish (IMHO) doesn't deal with it properly. Wasn't sure if anyone from Maven wanted to weigh in on the bug, that's all. Thanks again for the link. Best, Laird
