On Tue, Apr 14, 2009 at 10:34 PM, Adam Murdoch <[email protected]> wrote:
>
>
> Jeppe Madsen wrote:
>
>> Hi,
>>
>> We have a multiproject build where the output of some projects are just
>> jar files which are common to all the other webapps. These common jar files
>> should be on the container classpath and not included in each war file. How
>> can we specify that in Gradle?
>>
>> If we do
>> compile project(':common')
>>
>> The common project will (correctly) be compiled but the resulting jar will
>> be included in the war.
>>
>> If we do
>> providedCompile project(':common')
>>
>> The jar file (if it exists) will not be included in the war, but the
>> common project is not built....
>>
>> We currently do the first option and manually remove the common.jar from
>> the war, but maybe there's a better way?
>>
>>
> The second option is the correct way to specify this. Unfortunately, as
> you've found, this is broken in Gradle 0.5. It is fixed in trunk, so will
> work again in Gradle 0.6. In the meantime, you can use Steve's workaround.
Thanks (to both). Seems like there are lots of nice stuff in 0.6 (which
according to the release plan should be available....tomorrow :-)
/Jeppe
