Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44F9F68B.1050909@mobilebox.pl>
Date: Sat, 02 Sep 2006 23:24:27 +0200
From: Leszek Gawron <lgawron@mobilebox.pl>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: cocoon:deploy consider a dependency's scope?
References: <47f71d940609021200y5e21e352t8e361d00d9019e4d@mail.gmail.com>
 <44F9F33B.80804@mobilebox.pl>
In-Reply-To: <44F9F33B.80804@mobilebox.pl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Leszek Gawron wrote:
> Rice Yeh wrote:
>> Hi,
>>   Does cocoon:deploy consider a dependency's scope? I have a 
>> dependency whose scope is 'compile', hence it should not be deployed 
>> to WEB-INF/cocoon/lib/. But I find it is always deployed. So I use 
>> 'exclusion' to exclude it. But it is kind of workaround.
> Hmmm ... if you need something for 'compile' you need it also for 
> runtime, don't you?
> 
> What probably should be taken into account is 'provided', 'system' and 
> 'test' dependencies. I see in code this is probably not handled well.

- when building a webapp proper dependencies are copied to WEB-INF/lib 
by mvn war:exploded. This has got nothing to do with cocoon:deploy. 
cocoon:deploy only moves the resources to WEB-INF/cocoon/lib if you 
choose to use shielding classloader.

- when performing mvn cocoon:deploy for a development block the task 
itself copies the dependency jar files. It omits 'provided', 'system' 
and 'test' dependencies (system was ommited in current trunk - just 
fixed that).

-- 
Leszek Gawron, IT Manager                          MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65