[kepler-dev] classpath too long

[David Welker]

Hi Jared,

The source code for the jar file is the build system itself. In this  
case, I just changed "fork" to false in org.kepler.build.Run. Then, I  
issued the build command: "ant -f kepler-tasks.xml" and this rebuilt  
build-area/target/kepler-tasks.jar. I then renamed kepler-tasks.jar to  
"kepler-2.0-no-fork.jar" and emailed it to you.

I did not check in the changes to the build itself, because I think  
the typical default we want is to fork.

Let me know if that makes sense or if you have any questions. In the  
future, I will brainstorm better ways of handling these sorts of  
classpath issues on Windows, but this should work adequately for you  
now.

-David


On Apr 25, 2011, at 3:19 PM, Chase, Jared M wrote:

> Hi David,
>
> Thank you for this jar file.  It solved the issue.  Do you have the  
> source code for the jar?  I would like to recompile it to work with  
> java 5.
>
> Thanks!
> Jared
>
> -----Original Message-----
> From: David Welker [mailto:david.v.welker at gmail.com]
> Sent: Monday, April 25, 2011 2:17 PM
> To: Chase, Jared M
> Cc: Christopher Brooks; Elsethagen, Todd O; kepler-dev at kepler-project.org
> Subject: Re: [kepler-dev] classpath too long
>
> Hi Jared,
>
> I was wondering if you could replace your kepler-2.0.jar with the  
> following jar that is attached named kepler-2.0-no-fork.jar. By not  
> forking, it should avoid creating a long classpath. I have not been  
> able to test this, but it should work. Please let me know if this  
> solves the problem for you.
>
> David
>