Hi, Stefan.
Stefan Bodewig <[EMAIL PROTECTED]> wrote on 2005-06-22 11:51:32 AM:
> On Wed, 22 Jun 2005, Henry Zongaro <[EMAIL PROTECTED]> wrote:
> > Thank you for giving me access to that file. It confirmed my
> > suspicions about the reason for the failure. Actually resolving the
> > problem is going to be a much more difficult problem, though -
> > untangling the strange interactions between Gump's class path and
> > bootstrap class path settings and those of the Xalan build.
>
> In theory Gump controls all the classpath settings.
>
> Bootclasspath ought to be CVS HEAD of Xerces (which uses JAXP 1.3 by
> now), XML-APIs from xml-commons (ditto) and Xalan-J.
>
> All other stuff should end up on the normal CLASSPATH environment
> variable.
>
> Ant should be ignoring all other classpath setting you are making in
> any other place. If this is not what you see, please yell.
I had to put aside investigation of this problem for a time. I now
have a patch which I've asked another Xalan-Java committer to review.
However, I wanted to follow up on your comment about the class path
settings.
This Xalan-J smoketest problem shows up in a custom task that we
define (using "taskdef") in our ant build file. Our ant build file
specifies both classpathref and bootclasspath attributes on references to
this custom task using paths created within the build file, and the custom
task builds a CommandlineJava object that it uses to create another JVM
within which to run a test. When the smoketest is run by the Gump build,
my patch simply copies through the existing bootclasspath setting using
the value of the sun.boot.class.path property.
Does your comment about Ant "ignoring all other classpath settings"
apply to the classpathref and bootclasspath attributes we've specified on
our custom task? If so, that's not the behaviour we're seeing.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
