Re: cvs commit: logging-log4j build.xml

[Curt Arnold]

The entire lbel tree appeared to be dependent on StringCompator which 
was dependent on Jakarta-Oro.  The build file's lack of Oro checking on 
build-log4j strongly suggested that it was not intended for Oro 
dependent files to be compiled in that step and the lbel files were not 
included in the log4j.jar (or any jar as far as I can tell).

The changes move the compilation of the lbel tree to the build-oro step 
and includes the resultant classfiles in log4j-oro.jar.

In addition, the Kaffe GUMP builds were failing very early in the 
detection of JNDI where they got much further in logging-log4j-12.  I 
added "unless" clauses to the jndi and jaxp detection targets so that 
detection steps can be manually overriden so we can find out with gcj 
thinks about our source code.

I moved the "jaf" dependency to the logging-log4j-test project in the 
Gump descriptor.  Jaf did not appear to be required to build log4j, 
only to run the tests.  I don't think adding as a dependency for log4j 
would have implied that it was in the classpath for log4j-tests either. 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]