The update-jars target would bring down the dependant jars into your
${lib.repo} ( co jakarta-turbine-3 and try it ).
The old build files in jakarta-turbine-2/build use the jakarta-turbine-2/lib
directory. I guess that build stuff could be considered deprecated after
the other is working. Going into jakarta-turbine-2/build and building there
should have always worked and I'll leave that alone.
-----------------------------------------------------------------
Jeffrey D. Brekke Quad/Graphics
[EMAIL PROTECTED] http://www.qg.com
-----------------------------------------------------------------
> -----Original Message-----
> From: Paul Spencer [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 30, 2002 3:49 PM
> To: Turbine Developers List
> Subject: Re: cvs commit: jakarta-turbine-2 build-torque.xml
> build.properti es build.xml build-turbine-sql.xml
>
>
> Jeff,
> As a test, I recommend you do a fresh "cvs checkout" and then
> a build.
> Make sure only the jars downloaded by the "cvs checkout" are
> used in the
> build.
>
> Brekke, Jeff wrote:
>
> > With the recent Global Cache patch and test case which was
> written to use
> > cactus, I'm working on integrating some testing build xml's
> with t2 and will
> > add in Jason's update-jars target also. This should
> alleviate some of the
> > pain temporarily with building t2 from the build*.xml's in
> the root. I'll
> > leave the build/* stuff alone for now except to remove the
> compiling and
> > running of the test cases.
> >
> > -----------------------------------------------------------------
> > Jeffrey D. Brekke Quad/Graphics
> > [EMAIL PROTECTED] http://www.qg.com
> > -----------------------------------------------------------------
> >
>
> Paul Spencer
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
