Yeah. My goof. There's a test that runs ant targets that clean and build the
project. It needs to when run by itself but when run in the batch of tests
it breaks everything, obviously. I made it depend on a system property so
the clean could be disabled.
Thanks for your reply Antoine!
,chris
I must be missing something. The attached build.xml has a target "junit"
that causes the classes and test classes to be compiled to "build/..." and
then runs the tests. All the compiles work. The test get run. There are a
fair number of tests but after a few successes all the rest fail. All the
fai
remember to use the classloader that loaded the
> custom task as the parent for the new classloader
> created in the task.
>
> Peter
>
> On Wed, May 7, 2008 at 3:59 PM, Steve Loughran <[EMAIL PROTECTED]> wrote:
> >
> > Christofer Jennings wrote:
> >
> >
I think I have a classloader problem.
I've made a custom task that looks through classes for a method annotation,
then makes a report. I've got junit tests that work in my IDE showing that
the annotations can be found. But when I run the task the annotations are
not recognized. That is, the a
SOLVED
I narrowed the problem down to the weblogic servicegen task setup. When
using the ant task to call the nested build file, servicegen was not setup.
By using the exec task, the build file runs just the same as when run
directly, so the problem goes away.
Basically I changed the wrapper bui
Ninju,
Thanks for the reply. I tried forking the javac too, but got the same
results. I'm leaning more and more to thinking the problem is in the foo
build itself, and maybe the foo code. I found unused imports that caused the
EJB dependency, but taking them out lead to another EJB dependency tha
Follow up;
Looking further, I found that the foo/dto package does have a dependency to
foo/util/Bar.java ... So that part does make sense too.
But I still don't see the difference between running directly and using the
wrapper.
Still confused,
boz
On 6/12/06, Christofer Jennings &l
I'm having trouble with basedir (I think).
It all started with me trying to run a build.xml script from cruisecontrol
(CC). CC uses wrapper scripts to run project builds. I've run the wrapper
without CC and got the same results, so it's not CC. The wrapper build file
looks like this...
