What makes you think the issue is that the classpath is too long?
Could it also be an issue that your path has spaces in it?
I know we had issues with paths with spaces in them before, though I
am not sure what Chad Berkeley who know longer works on Kepler did to
address them.
-David
On Apr 25, 2011, at 10:06 AM, Chase, Jared M wrote:
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
_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
