Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 2411 invoked from network); 17 Dec 2009 14:00:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Dec 2009 14:00:50 -0000 Received: (qmail 47642 invoked by uid 500); 17 Dec 2009 14:00:47 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 47516 invoked by uid 500); 17 Dec 2009 14:00:47 -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 77988 invoked by uid 99); 17 Dec 2009 11:09:37 -0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) From: Marco Beelen To: "users@maven.apache.org" Date: Thu, 17 Dec 2009 12:09:11 +0100 Subject: enforce dependency to be set to provided Thread-Topic: enforce dependency to be set to provided Thread-Index: AQHKfwlcNKnEetOSCE+Mc23vt43mxA== Message-ID: Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, nl-NL Content-Type: multipart/alternative; boundary="_000_E6F4A6429FB291409920200BD5A1B10618ABF6FDDAiprofssvr_" MIME-Version: 1.0 --_000_E6F4A6429FB291409920200BD5A1B10618ABF6FDDAiprofssvr_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, For my portal I'm going to write various web-application and I want them to= reuse various libraries provided by my portal server. All the webapp proje= ct have the same parent. In order to prevent the webapps to include the dep= endency in the WEB-INF\lib, I wan't to configure a rule in the parent pom, = where I ban some library (log4j:log4j). The webapp are allowed to use the d= ependency, but only when the scope is set to provided. I tried the bannedDependency configuration like this: true log4j:log4j log4j:log4j:*:provided That doesn't work, because when I build a webapp with the log4j dependency = on compile scope, the enforcer plugin doesn't cause my build to fail, which= I would like it to. Any suggestions how to handle this? With kind regards, Marco Marco Beelen Software-architect +31(0)6 55 145 554 IPROFS Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl +31 (0)23 547 6369 --_000_E6F4A6429FB291409920200BD5A1B10618ABF6FDDAiprofssvr_--