Michael McCallum wrote:
IMO the log4j, logkit, avalon dependencies all need to go... I as I imagine most people do only use one logging implementation in the deployed systems why introduce a dependency on several implementations at the top level?

Commons-logging only has one level, the top level. So these all need to be in the one, and only, pom we have. If we decide in the future (not for this patch release) to "mavenize" commons-logging there would be a hierarchy of poms.

check out http://www.slf4j.com for an appropriate break up of the artifacts and use cases

I will not get into a debate on which logging library to use. The purpose of my first mail was to make sure that the pom for commons-logging is as good as it can be, for the way commons-logging works.

I've generally stopped using dependencyManagement in favour of dependency composition

On Tuesday 28 August 2007 10:06, Stephane Nicoll wrote:
For the servlet-api dependency, provided scope is enough (provided is
not transitive).

Thanks,
Stéphane

On 8/27/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi all

The poms for commons logging has taken some beating on this list over
the years. The reason for that has been the dependencies section.
Previous poms of commons-logging was created for Maven 1. These were
then converted into Maven 2 poms with various degree of success. In
particular the scope wasn't set properly.

We are now preparing the next release of commons-logging (version 1.1.1)
which will be built with Maven 2. That means that the pom that ends up
in the Maven 2 repository will be the same one that we have created.

To make sure that we have covered all bases this time we invite you, the
community, to help us get it right. The current pom.xml is available for
your viewing in our subversion repository:


https://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?revisi
on=568979&view=markup

Please post any comments you have on the pom to this list, and I will
bring the over to the commons community.

--
Dennis Lundberg
Apache Commons committer and PMC member

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



--
Dennis Lundberg


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

Reply via email to