[aargh - top-posting!]

It is true that SVN HEAD has a new dependency on servletapi.jar. But I
don't think that's the problem that spikesource are reporting.

The log file shown indicates a failure to compile the optional jar.

This might have been because:
(a) the version# is now included in the commons-logging jarfile name
(b) the version# in the main build.xml has been updated to 1.1-dev
(c) the version# in the optional build.xml was still 1.0.6-dev

The combination of all three may have meant that
commons-logging-1.1-dev.jar wasn't ending up in the compile path for the
optional jar.

I have fixed the version# in the optional build.xml file so maybe this
will fix the issue. 

Warning: currently commons-logging is going through some build process
changes, including debate about dependencies. So external build
processes may break over the next few weeks until this gets settled
down.

Surendra: In future when emailing to the [email protected]
(or commons-user) list it would be appreciated if you could put the name
of the component in the subject line (see this email). This is a shared
email list for multiple components and without this the email may get
missed by people interested in that component.

Regards,

Simon

On Wed, 2005-06-29 at 22:58 +0100, robert burrell donkin wrote:
> i think that JCL now needs servlet api 2.3 to build (but not run)
> 
> - robert
> 
> On Wed, 2005-06-29 at 09:38 -0700, Surendra Singhi wrote:
> > Hello,
> >   We are doing daily nightly build of commons logging, but due to some 
> > reason
> > the builds are failing.
> > This is the link to log file:
> > http://www.spikesource.com/spikewatch.logs/suse-92-i586/765/commons-logging/logs/commons-logging.build.maven.log
> > 
> > Can you please look at it and tell me, whether this failure is due to some
> > problem in commons-logging or are we missing some dependency.
> > 
> > This is the main page from where you can navigate around.
> > http://www.spikesource.com/spikewatch/index.jsp
> > 
> > Thanks.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


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

Reply via email to