Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44E4E1B6.2050300@j-hohwiller.de>
Date: Thu, 17 Aug 2006 23:37:58 +0200
From: Joerg Hohwiller <joerg@j-hohwiller.de>
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [logging] pom for commons-logging-api and building/testing JCL
 with Maven 1
References: <44DB7D07.4030001@apache.org>
	 <1a5b6c410608111015n1b4ba808n2c20a500309922a7@mail.gmail.com>
	 <44DCD46D.3090304@apache.org> <1155717838.5214.9.camel@blackbox>
 <44E37DDF.1050802@apache.org>
In-Reply-To: <44E37DDF.1050802@apache.org>
OpenPGP: id=60DCBFFF
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

-----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 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.
> 
I think it is a good idea to keep the tiny commons-logging-api as separate
artifact and allow people to only depend on that.

For the review of the pom.xml some comments from me:
- -consider about spitting off commons-logging-api as a separate project with its
own pom.xml. The build logic could be so much simpler.

- -what do you think about a common pom.xml for all commons?

- -whenever you swith to maven2 then you should switch to the default directory
layout

- -the profile based dependency stuff is also very complicated magic. Following
the maven2 conventions could make it a lot easier. But this might require that
 you split of the implementation (commons-logging-logj4, commons-logging-avalon,
etc.) then you even do not need to declare the dependencies optional - I gues
you are not looking foreward to do this (e.g. from the maintaince point of view)...

Regards
  J�rg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFE5OG2mPuec2Dcv/8RAow/AJ9mIdj40xd7kXwq0FSSVQ0oTnOTyQCfdmdn
UBpuYgDNsa82Z+V3DcRnH9U=
=V5TA
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org