Daniel Kulp wrote:
Can you describe what problem you had? Was it a compile time problem, a unit
test runtime problem? Other?
The compiler and test issues should be easily worked around. You can use the
dependency plugin to download the spec jar into target/lib or similar then
use the compilerArguements/argLine flags to control the compiler/surefire to
work. (Providing you use fork mode for both)
That sounds like a decent solution. I'll try that!
It should not be necessary to fork the compiler, by the way. In fact,
forking the compiler will not work on Windows, since Maven passes the
arguments on the command line, and Windows does not support the very
long command line parameters required to compile a large number of classes.
Regards,
Anders
