> on 9/29/2000 1:26 PM, "Christopher Elkins" <[EMAIL PROTECTED]> wrote:
>
> > What do you think about doing this for all services dependent on external
> > packages - e.g., CastorService, XmlRpcService? Then, we wouldn't have to
store
> > those jars in the turbine repository. For the TDK, we could grab them at
> > build-time and bundle them with the rest of the package. Thoughts?
>
> improving that process *and* integrating it into the TDK is fine by me.
>
A beneficial side-effect of this (and removing support for JDK 1.1) is that
we'll no longer need all those hard-coded classpaths in the build-scripts. We
can just use lib/*.jar.
Another improvement might be integrating some of Peter Donald's suggestions
regarding classpath construction within the build-*.xml files. This would allow
build-tdk to override build-turbine and insert the desired jars in the
classpath. After such a change, building TDK would not require building turbine
first; build-tdk would handle both steps for you and automatically compile all
"optional" services. Anyway, just a thought.
> i don't have the time/energy to do that though so if you want to, go for it.
>
Don't worry - I _am_ volunteering. :-) I just wanted to get some opinions
before proceeding.
> :-)
>
> -jon
>
--
Christopher Elkins
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
