[GRADLE-815] Jetty should be able to deploy multiple wars Created: 08/Feb/10 Updated: 16/Jan/17 Resolved: 16/Jan/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9 |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Spencer Allain | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 5 |
| Description |
|
The jetty plugin currently assumes and only allows for a singular WAR file to be associated with the runJettyWar task. Jetty supports multi-war deployments. This could be enhanced to allow it to deploy more than one WAR file, and simply separate them out in the build/jetty directory by war names (which is commonly done by servlet containers anyway). This allows for test deployments where login or other shared functions are handled by one war, and various specialized functions are actually maintained within separate wars. The closest workaround is to attempt to merge web.xml files for the multiple wars and hope that individual jsp or other files do not have identically named files (like index.jsp) and rename those that do, and update references to them elsewhere. Obviously this is difficult to get working for unit testing. |
| Comments |
| 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 [ 16/Jan/17 ] |
|
The Jetty plugin has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore. |