Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 35300 invoked from network); 21 Jul 2008 08:51:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jul 2008 08:51:07 -0000 Received: (qmail 64417 invoked by uid 500); 21 Jul 2008 08:51:04 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 64360 invoked by uid 500); 21 Jul 2008 08:51:04 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 64349 invoked by uid 99); 21 Jul 2008 08:51:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jul 2008 01:51:04 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [91.135.15.56] (HELO haggis.mythic-beasts.com) (91.135.15.56) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jul 2008 08:50:09 +0000 Received: from [93.93.130.49] (helo=sphinx.mythic-beasts.com) by haggis.mythic-beasts.com with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.63) (envelope-from ) id 1KKr0N-0008R3-N7 for users@cocoon.apache.org; Mon, 21 Jul 2008 09:44:27 +0100 Received: from host-84-9-158-18.dslgb.com ([84.9.158.18] helo=[192.168.1.53]) by sphinx.mythic-beasts.com with esmtpa (Exim 4.62) (envelope-from ) id 1KKr6D-00050V-31 for users@cocoon.apache.org; Mon, 21 Jul 2008 09:50:29 +0100 Message-ID: <48844DD0.7040804@searchevent.co.uk> Date: Mon, 21 Jul 2008 09:50:24 +0100 From: David Legg Organization: SearchEvent User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: C2.2 - Cannot remove jar files from classpath using Maven References: <48833BBC.90107@searchevent.co.uk> <4883536F.5030103@apache.org> <48837C79.40001@searchevent.co.uk> <20080721071304.134740@gmx.net> In-Reply-To: <20080721071304.134740@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mythic-Sender-Verify: + host 212.69.37.6 accepted RCPT TO with '250 Accepted' X-BlackCat-Spam-Score: -13 Received-SPF: none (sphinx.mythic-beasts.com: domain of david.legg@searchevent.co.uk does not designate permitted sender hosts) client-ip=84.9.158.18 envelope-from=david.legg@searchevent.co.uk helo=[192.168.1.53] X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-1.4 Hi Patrick, > Just for getting it clear - is 'myblock' some block, or are you listing dependencies for the whole web-application, since there could be a dep on commons-logging wich is not mentioned out of 'myblock' > I realised my message was a bit ambiguous after I sent it. To be clear, 'myblock', is *exactly* the same as 'myBlock1' in the tutorial [1]. All I did to get the dependency tree listing was to add some tags to the myblock/pom.xml file to exclude commons-logging and log4j jar files from all of the dependencies listed in the pom. The reason I'm flagellating myself like this is because I need to effectively replace these two jar files with some slf4j equivalents that redirect log messages created using legacy (commons-logging and log4j) code to the slf4j logging framework. Since that message and thanks to the hint about 'mvn dependency:tree' from Reinhard I've realized that only cocoon-core has a dependency on those two jar files. I updated pom.xml to only have the tags on cocoon-core and now the dependency tree shows no reference to the two jar files I wanted to be excluded. This is great!... but my quest to use slf4j as my logging solution is still not fulfilled. The question now is why when I run 'mvn package' or 'mvn jetty:run' when in the myblock directory does maven insist on placing the commons-logging and log4j jar files into WEB-INF/lib even though I've expressly excluded them? Maybe the answer has something to do with the cocoon-maven-plugin? Also, since my last message, I came across the Shielded Classloader [2] which explicitly mentions the problem of using your own logging framework and how the shielded classloader may help. I'm hoping that once I have these issues sorted out I'll write it up to help others travelling this route for the first time. Regards, David Legg [1] http://cocoon.apache.org/2.2/1159_1_1.html [2] http://cocoon.apache.org/2.2/maven-plugins/maven-plugin/1.0/1262_1_1.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org