commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <>
Subject Re: [logging] tests
Date Sat, 01 Oct 2005 02:58:01 GMT
On Sat, 2005-10-01 at 02:47 +0200, Joerg Hohwiller wrote:
> As I have checked with offical releases ant seems
> to be the master and maven is just there for other reasons (maybe the site
> generation).

Yes, this is the case. 

Up until now, commons-logging has always been built with Ant, with Maven
just used for the website.

After the last release I put some significant work into trying to use
Maven to build and test commons-logging. However the situation where we
need to bundle loggers for log4j12 and log4j13 but these two libraries
are binary-incompatible makes it even harder to use Maven.

Unfortunately, the result of my work is that the maven build initially
looks like it might be usable, but actually isn't. I really should strip
out all the code that even attempts to build the release jar.

> For me the question is:
> Is the API-jar build in maven.xml just legacy and can be kicked out?
> Or on the other hand has someone evaluated if the test issue can be solved with
> a recent maven version and the ant can be replaced and kicked out?

As you may have seen, the way unit testing is done has undergone a
radical revision (by me). It was extremely convoluted before, and is
hopefully now saner. I hoped that one of the outcomes was to be able to
build/test from maven, but the log4j incompatibility issues then blew
that goal out of the water again.

And unfortunately 2 months ago I ran out of time for working on
commons-logging (combination of new relationship and new job; need 25
hours in the day *without* any open-source work!).

If you think you can get this application building with Maven, then
please have a go. It will be a challenge.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message