buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Modrzyk" <hellon...@gmail.com>
Subject Re: include dependencies
Date Thu, 04 Sep 2008 01:40:37 GMT
really late answer, but yes, that does the trick perfectly.
Thanks !

On Fri, Aug 29, 2008 at 5:01 AM, lacton <lacton@users.sourceforge.net> wrote:
> On Thu, Aug 28, 2008 at 4:25 AM, Nicolas Modrzyk <hellonico@gmail.com> wrote:
>> Hi,
>>
>> I have the following situation.
>> I have a first project describe as:
>>
>> define "ui-fw" do
>>    package(:jar)
>>    package(:war).with(:libs=>libs)
>>  end
>>
>> and another one,
>> define "ui-fw-portlet" do
>>    libs = projects("ui-fw"), ...
>>    compile.with libs
>>    package(:war).with(:libs=>libs)
>>  end
>>
>> My problem being that buildr 1.2.10 is including the war file of ui-fw
>> as part of the war file of ui-fw-portlet.
>> Is this solved in 1.3 ? Or should I specifically exclude the war
>> artifact from the second package call ?
>
> Here's the way I would do it.
>
> <code>
> define 'ui-fw-portlet' do
>    compile.with project('ui-fw').package(:jar), ...
>    package :war
> end
> </code>
>
> Since project('ui-fw') creates several packages, you need to specify
> which one you want for ui-fw-portlet.
>
> Note that the War task is clever enough to automatically include the
> compile dependencies, so no need for :libs in this example.
>
> Lacton
>

Mime
View raw message