Laird and Team yep..known issue ...push any environment variable such as CLASSPATH over 64k or any build-string over 2k do a "cmd.exe /C java.exe %MASSIVE_CLASSPATH% MyFile.java"
and watch the fireworks My workaround surefire limited to 2.4.2 ..anything above that and surefire will attempt to construct an extended classpath <forkMode>never</forkMode> Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > From: [email protected] > Date: Tue, 9 Apr 2013 21:06:40 +1000 > Subject: Re: maven-compiler-plugin, fork, and Windows classpath length > To: [email protected] > > btw that will fix the issue for forked compilation only (not for in > process compilations) > > 2013/4/9 Kristian Rosenvold <[email protected]>: > > 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] > > > > > > -- > 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] >
