[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=all ] Max Andersen resolved JBIDE-1231. --------------------------------- Resolution: Done Ok - I actually can't reproduce this. Only in the case of the jboss server *not* running are changes not deployed; which is what WTP does - it doesn't publish anything if ther server is not running. Gavin - please reopen this if you can reproduce the situation; both touch descriptors etc. works for me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=comments#action_12385360 ] Gavin King commented on JBIDE-1231: ----------------------------------- Actually I'm still experiencing this intermittently, but Max says the new build should fix it. We'll see... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=comments#action_12385601 ] Rob Stryker commented on JBIDE-1231: ------------------------------------ any update here? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=all ] Max Andersen resolved JBIDE-1231. --------------------------------- Resolution: Cannot Reproduce Bug we can't reproduce this now - reopen if still issue with later builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=all ] Gavin King reopened JBIDE-1231: ------------------------------- I experienced it again with last nights build, on a WAR project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=all ] Gavin King updated JBIDE-1231: ------------------------------ Priority: Critical (was: Major) OK, now I understand it! The problem is that there is a bug in JBoss 4.2.2, so JBoss watches the timestamp of the EAR *directory*, not of the deployment descriptor! So we should try to touch the directory as well as the descriptor when we want to force a restart. *phew* -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=all ] Gavin King updated JBIDE-1231: ------------------------------ Summary: Touching deployment descriptor does not restart EAR deployment on JBoss 4.2.2 (was: Incremental deployment stopped working (at least for EAR)) Reporter: Gavin King (was: Max Andersen) To be clear, this is not a bug in JBoss Tools, it is a bug in JBoss AS 4.2.2, but needs a workaround in JBoss Tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=all ] Max Andersen updated JBIDE-1231: -------------------------------- Priority: Optional (was: Critical) http://java.sun.com/developer/technicalArticles/Intl/USDST/: ""Problems Affecting Java Applications The Java Runtime Environment (JRE) stores rules about DST observance all around the globe. Older JREs will have outdated rules that have been superseded by the Energy Policy Act of 2005. As a result, applications running on an older JRE might report incorrect time from March 11, 2007, through April 2, 2007, and from October 29, 2007, through November 4, 2007." Let's wait and see if the problem persists after 4th november... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=comments#action_12386071 ] Gavin King commented on JBIDE-1231: ----------------------------------- "When do we want to restart the module for the user? It'd be inefficient to restart the module after every incremental publish, because then every time the user changes a jsp or html file, the module must essentially re-deploy." Of course we don't want to do that! We would kill the permgen in seconds! Please no. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1231?page=all ] Max Andersen resolved JBIDE-1231. --------------------------------- Resolution: Cannot Reproduce Bug I will assume this was caused by the DST time shifts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira