commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Hohwiller <>
Subject Re: [logging] tests
Date Sat, 01 Oct 2005 00:47:53 GMT
Hash: SHA1

Hi there,
> [snip]
> So I will adopt the build-process so the AbstractLogger will be included in the
> API jar. I suppose I have to do this in the ant and in the maven build
> configuration.
> [snip]
Just to point this out: the API jar already contained the AbstractLogger class
when it was build with maven. The maven build process is a very different animal
and especially the ant build says in the API jar comes exactly what is specified
by includes while the maven.xml says in the API jar comes everyting except some
The result completely differs. As I have checked with offical releases ant seems
to be the master and maven is just there for other reasons (maybe the site
I think this is not really nice but in this situation hard to maintain.
If the maven can build the api jar at all it should do right in my oppinion.
For maintainance the redundancy could be avoided by having one XML snipplet for
that logic and include it within and and maven. The tradeoff is a more
complicated situation.

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?

Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -


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

View raw message