[GRADLE-510] behaviour of dependencies of WAR plugin in a multiple project environment Created: 28/May/09 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Attachments:||base.build.gadle jar.build.gradle war.build.gradle|
when packaging the WAR file, we wish to package in lib folder:
The question is:
The second question needs a test case.
I've included 3 files as a base for a test case (didn't test them, but main idea is there).
|Comment by Hans Dockter [ 28/May/09 ]|
Thanks a lot.
|Comment by Mauro Molinari [ 24/Nov/11 ]|
Forgive me if I don't understand the description of this bug properly.
I think those dependencies should NOT be included in A.war, unless some other project A depends on declare them as standard compile/runtime dependencies.
|Comment by Benjamin Muschko [ 15/Nov/16 ]|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 10/Feb/17 ]|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.