John Morrison wrote:
>
> I modified build.xml slightly to exclude the dist directory. This
> fixes the recursive zip problem, but it would be better for the
> junit guys to improve their build structure. Do you know any of
> them?
No, I don't. You are correct, the right fix is to engage the junit folks.
Care to try?
> I've also attached a (modified from C2) build.sh with ant and xalan
> are in the root of junit. When I build JUnit through this I don't
> get any exceptions. Is this useful information?
I finally figured it out. There is a unit test which is designed to ensure
that a given class is loaded from a specific jar. As gump controls the
classpath (and specifically, because my default classpath includes ".", and
the junit build places the build outputs in the same directory as the
source), this test fails. I can probably figure out a way to avoid this
particular problem, but the right fix (IMHO) is to have the junit folks
improve their build structure - though I don't like the sound of that
either, as I don't want folks to get the impression that they need to
adjust their build structure to meet the requirements of gump.
> Is the 'JAVA Result' at the end of the junit build the same?
I get a -1.
> Building JUnit from the cmd line I don't get a java result.
You actually do, but the shell you are using by default doesn't show it.
Some shells do.
> Shouldn't a 'Java Result' mean failure to build?
If would if failonerror="true" was specified in the <java> element in the
build.xml.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
