[GRADLE-811] War overlays Created: 06/Feb/10 Updated: 08/Feb/17 Resolved: 08/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature | ||
Reporter: | Aaron Hamid | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 24 |
Description |
It would be cool if Gradle supported some notion of war overlays/compositing (http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html) out of the box (integrated with dependency management). We rely on this feature rather extensively to perform customizations of third party war files. |
Comments |
Comment by Davide Cavestro [ 26/Aug/11 ] |
Really needed for customizing web applications (even home made) and getting a good IDE integration even for war projects (take a look at STS-1314 discussion). |
Comment by Davide Cavestro [ 10/Oct/11 ] |
I hope this issue should not remain a minor priority RFE. |
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 [ 08/Feb/17 ] |
From my perspective you should be able to achieve the same behavior with methods already exposed by AbstractCopyTask which effectively is being used by the War task. You can easily merge existing WARs into other WARs, filter files as you merge them and exclude any files you need to filter. I am going to mark this issue as "Won't fix". Please open an issue on GitHub if you feel like your use case isn't fulfilled. |