Hi Simon
I think this is a Maven 1 vs Maven 2 issue. As long as we deploy our
artifacts (jars) to the Maven 1 repo, which we will do until we switch
to Maven 2 as a build system, we need to also supply Maven 1 poms for
them. The reason I created this pom was that the deployed
commons-logging-api.jar does not have an accompanying pom. Adding this
pom to the repo means that other products can set up commons-logging-api
as a dependency.
--
Dennis Lundberg
Simon Kitching wrote:
Hi,
I'm a little puzzled by this.
I have recently created a completely functional pom.xml file for
logging, which is checked in in trunk.
This pom declares all dependencies as optional (except when compiling a
checked-out svn release), so I think the same file is suitable for use
as a pom for commons-logging-api.jar without modifications.
Regards,
Simon
On Fri, 2006-08-11 at 21:03 +0200, Dennis Lundberg wrote:
Carlos Sanchez wrote:
If it's this one
http://svn.apache.org/viewvc/jakarta/commons/proper/logging/trunk/commons-logging-api.pom?view=markup
Yes, that's the one.
I'd remove optional from both dependencies, it's not needed being
scope test or plugins.
Done. Thanks for reviewing.
So it has no dependencies at all, isn't it?
Yes, it doesn't have any dependencies.
---------------------------------------------------------------------
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]
