I think we solved all of that with the "CLASSPATH" env var in surefire; I believe it pushes the limit to 64K.
64K must be enough for everyone :) Kristian 2013/4/9 Olivier Lamy <[email protected]>: > uhm maybe with setting env var CLASSPATH (I think surefire do that) > BTW add a jira entry (note: I don't have windauze to test the change :-) ) > > 2013/3/23 Laird Nelson <[email protected]>: >> I am using maven-compiler-plugin version 3.0. We use fork=true. >> >> We are seeing (I am pretty certain; haven't sorted through the boatloads of >> -X output yet) that the classpath being supplied to the >> maven-compiler-plugin is too long for Windows. (We're getting some weird >> errors out of the underlying compiler, then when we shorten the root path >> where we have the project the errors go away.) >> >> I didn't see any way to have Maven supply the classpath to the >> maven-compiler-plugin as a file, or any other way to bypass the Windows >> path length limitation. >> >> Is this a known issue? I also didn't see it when I did a "classpath" >> search in Jira under the MCOMPILER project, but there were lots of entries >> so I might have missed it. >> >> Thanks, >> Best, >> Laird >> >> -- >> http://about.me/lairdnelson > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
