[GRADLE-1269] Project applying War plugin can no longer be used as project lib dependency Created: 22/Dec/10 Updated: 04/Jan/13 Resolved: 16/Oct/11
|Reporter:||Peter Niederwieser||Assignee:||Adam Murdoch|
As soon as the War plugin is applied to a project, that project can no longer be used as a project lib dependency, even if jar.enabled is set to true. It seems as if the project's classes were no longer added to the dependent's compile class path.
|Comment by Daniel Bartl [ 16/May/11 ]|
Following is the description of the possible workaround that solved the problem for me at the moment
"A work around is to enable the 'jar' task, and add it back to the 'archives' configuration:
jar.enabled = true
It's not a perfect work around, in that you end up with both the jar and war in the compile and runtime classpath, which can be a problem if you then bundle some kind of distribution, or another war, in a dependent project."
|Comment by Scott Yancey [ 22/Jun/11 ]|
Is there any plan to address this completely? Meaning, a way to include the project simply in jar format only, without also pulling in the war?
|Comment by Spencer Allain [ 05/Jul/11 ]|
This is duplicated in gradle-687, but there might be different watchers.
While not particularly pretty, and uses an internal api, this gets rid of the war file from the archives (and the classpath), so that normal dependencies work.
You can also check the mailing list, where I describe this pattern, plus some additions that allow for easily wiring up multiple wars to one or more ears.