commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Lundberg <denn...@apache.org>
Subject Re: [Logging] Ant build script broken?
Date Thu, 26 Jan 2006 21:38:36 GMT
robert burrell donkin wrote:
> On Thu, 2006-01-26 at 11:08 -0800, Craig McClanahan wrote:
> 
> hi craig
> 
>> The Ant build.xml file for [logging] has started failing for me, which
>> causes cascading failures in the nightly builds for a bunch of other commons
>> packages.  The error I get, when running "ant clean dist" is:
>>
>> BUILD FAILED
>> /home/craigmcc/Apache/jakarta/commons/trunks-proper/logging/build.xml:625:
>> /home/craigmcc/Apache/jakarta/commons/trunks-proper/logging/dist/docs/apidocs
>> not found.
>>
>> Could someone take a look at this and see if its something that needs to be
>> fixed, or tweaked in my configuration?
> 
> oop 8-)
> 
> i've been updating the build script to use maven generated documentation
> (amongst other things). i forget to test a completed clean build (before
> maven has been run). 
> 
> i've committed a fix and hopefully the nightly should run ok now. 
> 
> - robert

I added a warning message as well so that the release manager will be 
notified that the documentation distribution will be empty.

While doing this i noticed that there are still some remains from the 
log4j 1.3 build. The jar is defined in build.properties.sample and there 
is a warning message shown in build.xml if the jar is not present. Shall 
I remove these?

-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message