[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Xiao resolved GERONIMODEVTOOLS-790.
--------------------------------------
Resolution: Fixed
Fix Version/s: 3.0
> Application started twice
> -------------------------
>
> Key: GERONIMODEVTOOLS-790
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-790
> Project: Geronimo-Devtools
> Issue Type: New Feature
> Components: eclipse-plugin
> Affects Versions: 3.0-beta-1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> Say we have an application that is already deployed to the server and the
> server is stopped. Now, the application is modified while the server is
> stopped and server restarted. What happens is that when server starts up, it
> will start the "old" version of the application. And after the server is full
> started, Eclipse will automatically deploy the "new" application. That's
> usuallly ok but if you are dealing with large applications or applications
> that take some time to initialize that's very painful.
> So the idea here is that when such case happens only the "new" version of the
> application is deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
