-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Dennis Lundberg wrote:
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
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
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
If it's this one
http://svn.apache.org/viewvc/jakarta/commons/proper/logging/trunk/commons-logging-api.pom?view=markup
I'd remove optional from both dependencies, it's not needed being
scope test or plugins.
So it has no dependencies at all, isn't it?
On 8/10/06, Dennis Lundberg [EMAIL
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
Hi all
I've checked in a pom for commons-logging-api that is meant to be
deployed to the Maven repository. Before I deploy it I would like for it
to be reviewed. The reason for this file can be found in the archives [1].
Sorry it took so long, but I set the goal a little higher than just
