Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 64842 invoked from network); 28 Aug 2007 11:28:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Aug 2007 11:28:55 -0000 Received: (qmail 61044 invoked by uid 500); 28 Aug 2007 11:28:43 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 60994 invoked by uid 500); 28 Aug 2007 11:28:43 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 60983 invoked by uid 99); 28 Aug 2007 11:28:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 04:28:43 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [134.98.65.23] (HELO vwall-vs.elsag.de) (134.98.65.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 11:29:32 +0000 Received: from esmail.elsag.de ([192.168.2.88]) by vwall-vs.elsag.de with InterScan Messaging Security Suite; Tue, 28 Aug 2007 13:28:16 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Subject: RE: Community review of the next commons-logging pom Date: Tue, 28 Aug 2007 13:28:16 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Community review of the next commons-logging pom Thread-Index: AcfpZNAwhv1wn8kuRxaZpjtyqU2Z4wAAKC2g References: <46D3184D.2060702@apache.org> <200708281033.51030.gholam@apache.org> <200708282315.05830.gholam@apache.org> From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: "Maven Users List" X-Virus-Checked: Checked by ClamAV on apache.org Michael McCallum wrote on Tuesday, August 28, 2007 1:15 PM: >> Why? Only with dependencyManagement you're able to manage transitive >> versions. > In order to keep clean dependency graphs I have used standard > OO principles to > encasulate functionality in this case I will use spring as an example. >=20 > Spring provided many artifacts. I have many projects that use > different groups of spring projects so I have pulled the spring > dependencies=20 > out into two > compositions one that deals with contexts and the other persistence. [snip] You still did not explain, what "composition" means. It's no word used = in standard Maven terminology. Your description does not make it clear = what you *actually* have done. [snip] >> Commons logging has a different philosophy. But this is OT > for this list. > If the difference in philosophy means more difficulty in > managing dependency > graphs then its not OT for this list but very pertinent. It is OT, since it is up to the Apache Commons community how they carve = their artifacts. And splitting an artifact into 6 where 5 of them = contain a single wrapper class is where philosophy starts. You may = discuss this at Apache Commons. - J=F6rg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org