1. developers can use junit standlone test runner.
2. developers can use the junit ide integration (Eclispe has fantastic
support, and I am sure othere IDE`s also supports junit).
3. you can create an build file that will invoke the junit task for the
automated testing.
Chun Ji wrote:
> We hav
try to use explicit target directory in whatever task you are running,
and point it to the shadow directory.
David Carson wrote:
> We have a build environment where we build a 'shadow' of our source
> tree consisting of symbolic links to the real source tree. The actual
> build takes place in
There used to be a bug in eclipse where it ran ant with the wrong
working directory.
this could be the reason.
if you are not already doing it, use the latest eclipse (3.2 at the moment).
Robert Segal wrote:
Having some issues debugging with Eclipse and ANT. I have some build
scripts setu
> ant 1.7.0:
>
>
>
> outputdirectory="build/src">
>
> includes="*.jar"/>
>
>
>
>
>
> One may also put the antlr.jar file in ~/.ant/lib or in $ANT_HOME/lib.
>
> Peter
>
> On 2/25/07, Omry Yada
gt; assuming you have ant-junit.jar under $ANT_HOME/lib (which is the
> default if you use one of our releases) and you have a subdirectory
> lib/junit with junit-x-y-z.jar in it in, relative to the basedir of
> the build file.
>
> Best regards,
>
> Antoine
>
>
> On Feb 25, 2
is it possible to add the reference to the required jars for an optional
task as a part of the build.xml?
similar to the way I can add my own tasks and keep them with the build.xml
this will make build files much more portable across different machines,
because it will be possible to bundle the
