Replying to myself :
I've just found out that, given the size limitation for a windows environment,
I was lucky
that my "workaround" worked.
Sorry, just forget my question.
----- Mail original -----
De: "Stephane Gallès" <stephane.gal...@free.fr>
À: dev@gradle.codehaus.org
Envoyé: Samedi 14 Septembre 2013 23:30:28
Objet: [gradle-dev] JavaExec and command line length for windows
Hi,
using the JavaExec task, I was hit by the Windows command line length
limit (because of the length of the classpath I was using, and also because
the path are rather deep in the Gradle cache).
As a workaround, I did not use the 'classpath' feature of the task, and I used
the 'environment' feature : I set my classpath in the CLASSPATH env variable
instead.
I was wondering if the CLASSPATH env variable was considered at some point as a
default implementation to
set the classpath in the JavaExec task in order to protect the user from this
error ?
Thanks
Stephane
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
