On first glance, that seems like an error from the OS, saying the
command line is too long.
However, I am surprised that Maven would be invoking javac with a
command line. I expected that Maven would invoke the compiler in the
same JVM (no command line). If there is some part of your build that
is keeping Maven from invoking javac within the same JVM, you might
consider finding a way to eliminate the "forced forking".
Hi.
This is set in the version of the compiler tag I sent in your other
thread: and this seems to be related to that error. So there are a
couple of observations here:
I had also included the fork directive in the Maven configuration since
Maven had complained about some other problem when that was not
specified: there was some feature that wasn't supported unless the
process was forked. So you might try eliminating that and see your
other problem go away!
See the other thread for a thought about why that exception is showing up.
Steven.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
