[GRADLE-671] Option to fork the jetty process Created: 01/Oct/09 Updated: 16/Jan/17 Resolved: 16/Jan/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 0.7, 0.8 |
Fix Version/s: | None |
Type: | New Feature | ||
Reporter: | Jason Porter | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 2 |
Description |
There is currently the daemon option which stops the jetty process from blocking, but doesn't actually fork the process. When the build script finishes the server is also terminated. The ability to fork the jetty process would help development time as the developer can start the server forked and continue to make changes. Jetty can then pick up changes to the war or classes and reload those changes effectively creating something similar to a hot deploy. Eliminating (or at least cutting down) the deploy phase of JEE development is always a plus. |
Comments |
Comment by Jason Porter [ 02/Oct/09 ] |
According to the jetty folks this would have to be done via gradle calling Jetty. In Jetty7 it's possible, but not in Jetty 6: 11:56:55 < lightguard_jp> When using the embedded jetty (calling the APIs directly) is there a way to spawn the server process into a different thread or JVM? |
Comment by Jason Porter [ 22/Apr/10 ] |
We may want to wait on this, or we'd have to upgrade to a newer version of Jetty. Hans if you're in IRC we can discuss this and the glassfish plugin I've been toying with. |
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. |