[GRADLE-584] War plugin does not create build dependencies on Runtime configuration Created: 08/Aug/09  Updated: 04/Jan/13  Resolved: 08/Aug/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.7
Fix Version/s: 0.8

Type: Bug
Reporter: Steve Appling Assignee: Steve Appling
Resolution: Fixed Votes: 0


The war plugin bundles up the files in the runtime configuration to package in the resulting war. It does not however, depend on the projects in this configuration so they may not be build. This causes the current java multiproject sample to fail in a clean directory with "gradle dists".

Curiously it does not currently cause any integration tests failures. I'll add tests for this case.

One other note, this was previously working because tests (which were run because of the previous dependencies of the Java plugin) were adding the dependencies needed to build the dependent project. If you have run tests in the past, the needed api-1.0.jar has already been built and uploaded to the internal repository. This will then cause dists to work - EVEN AFTER A CLEAN since clean does not remove the jars from the internal repo. I think this is bad and will file another Jira to discuss getting clean to remove internal repo jars.

Comment by Steve Appling [ 08/Aug/09 ]

Revision 1731 includes this fix.

Generated at Wed Jun 30 11:33:40 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.