Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 53134 invoked from network); 22 Feb 2008 16:09:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2008 16:09:51 -0000 Received: (qmail 3711 invoked by uid 500); 22 Feb 2008 16:09:45 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 3677 invoked by uid 500); 22 Feb 2008 16:09:45 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 3668 invoked by uid 99); 22 Feb 2008 16:09:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 08:09:45 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=RCVD_NUMERIC_HELO,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [213.86.32.131] (HELO mobile.synchronica.com) (213.86.32.131) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 22 Feb 2008 16:09:11 +0000 Received: from 62.220.6.42 ([62.220.6.42]) by CEXCS001.SYNCHRONICA.COM ([192.168.1.5]) with Microsoft Exchange Server HTTP-DAV ; Fri, 22 Feb 2008 16:09:41 +0000 Received: from davidr-laptop by mobile.synchronica.com; 22 Feb 2008 17:09:17 +0100 Subject: Excessive Maven dependencies in parent pom -- move to core? From: David Rauschenbach To: dev@jackrabbit.apache.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Synchronica Date: Fri, 22 Feb 2008 17:09:17 +0100 Message-Id: <1203696557.8026.67.camel@davidr-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 X-Virus-Checked: Checked by ClamAV on apache.org Anyone have thoughts on all the dependencies for the entire Jackrabbit project are in the parent pom? Some of us are only writing SPI's, and we're getting transitive dependencies in our projects like nekohtml, pdfbox, derby, etc... that really have no business being there, and are causing us licensing hassles. I'm accumulating massive excludes wherever I depend on a Jackrabbit module, but it seems counter-intuitive, because I never know if I'm excluding an ACTUAL dependency. Thoughts? David