[
https://jira.jboss.org/jira/browse/JBAS-7467?page=com.atlassian.jira.plug...
]
Jason T. Greene updated JBAS-7467:
----------------------------------
Fix Version/s: Unscheduled
(was: 6.0.0.M3)
Unscheduling due to inactivity. Reassign to a release that you feel comfortable resolving
this issue in, or leave as is.
Add support for lazy on first request redeploy
----------------------------------------------
Key: JBAS-7467
URL:
https://jira.jboss.org/jira/browse/JBAS-7467
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers
Reporter: Jason T. Greene
Assignee: Jason T. Greene
Fix For: Unscheduled
Currently if JBoss IDE makes changes to an exploded deployment, and those changes include
deploy descriptor updates, the AS immediately redeploys. This can become timeconsuming if
the developer is making lots of individual changes. In a discussion with Gavin, he
suggested instead of requiring an explicit action of some sort (touching a magic file,
hitting a special button), we could also hold off on the redeploy until the first request
happens. This could be done on both web and remote invocations.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira