:40 +1000
> Subject: Re: maven-compiler-plugin, fork, and Windows classpath length
> To: users@maven.apache.org
>
> btw that will fix the issue for forked compilation only (not for in
> process compilations)
>
> 2013/4/9 Kristian Rosenvold :
> > I think we solved all of t
btw that will fix the issue for forked compilation only (not for in
process compilations)
2013/4/9 Kristian Rosenvold :
> 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
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 :
> uhm maybe with setting env var CLASSPATH (I think surefire do that)
> BTW add a jira entry (note: I don't have wi
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 :
> I am using maven-compiler-plugin version 3.0. We use fork=true.
>
> We are seeing (I am pretty certain; haven't sorted through
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 underlyin
