[news.eclipse.tools] Re: Seperate runtime classpath

["Stef van Dijk" <Stef_van_Dijk@xxxxxxx>]

How are you specifying the additional jars in the class path? Are you adding
them using "Add JARs..."?
I would expect that if you added them using "Add External JARs..." (or
better yet, using "Add Variable..."), you should be able to simply replace
the jars out in the file system without it ever causing a recompile of your
project. But I could be wrong.

   Stef

"David Wegener" <wegener@xxxxxxxx> wrote in message
news:3B7A860C.17DA283E@xxxxxxxxxxx
> Is there a way to specify a runtime classpath that is separate from the
> build classpath for Java projects.  We run our applications on a
> framework which has a number of jar files.  However, only the base jar
> file is required for builds.  The additional jars are required only to
> run the application.  Only being able to specify a build class path
> means that all of the jars need to be included there.  This causes a
> complete rebuild of the project if one of the jar files is changed.
> Being able to specify a separate runtime classpath would allow for quick
> swapping of jar files  without the rebuilds.
>
> Thanks
> Dave Wegener <wegener@xxxxxxxx>