Hello,

When I setup a kepler developer environment on windows in a location that has a 
longer path than 'c:\kepler', such as 'c:\Documents and 
Settings\username\kepler', kepler generates a classpath that is too long for 
windows and my workflow is unable to run.

It is important to us to allow our users to install kepler wherever they would 
like.  Is there a workaround that someone has found to address this?

Thanks!
Jared

_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev

Reply via email to