> on 11/12/2000 2:34 PM, "Christopher Elkins" <[EMAIL PROTECTED]> wrote:
>
> > I've actually done this already. The Turbine build scripts now do nothing
more
> > than build the minimal classpath required for Ant and launch it. Indeed, you
> > can
> > now build Turbine by calling:
> > $ANT_HOME/bin/ant -buildfile build-turbine.xml [target]
> >
> > where the current directory is turbine/build and ANT_HOME points to Ant 1.2
or
> > higher.
>
> Ok, this is what I was looking for. :-) Thanks Christopher.
>
Just a quick follow-up...
While setting the classpath in build.xml generally works, be aware that you must
pass this classpath to an ungodly number of tasks. (In fact, I just updated
Turbine CVS with some changes that fixes such problems in the
"check_for_optional_packages" target.)
There still remains one oustanding issue in build-turbine.xml with respect to
the JUnit-calling targets ("run-tests" and "run-singletest"). No matter what
I've tried, I always get the following error:
C:\Projects\jakarta\turbine\build\build-turbine.xml:378: Could not create task o
f type: junit because I can't find it in the list of task class definitions. Co
mmon solutions are: 1 execute bin/bootstrap. 2 use taskdef to declare your task.
3 add the task to defaults.properties.
I have verified that the properties file in ant-1.2.jar does indeed contain an
entry for the junit task, so I suspect some sort of classloader issue. Ugh.
> -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]
