[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-1231) Incremental deployment stopped working (at least for EAR)
Gavin King (JIRA)
jira-events at lists.jboss.org
Fri Nov 2 15:32:44 EDT 2007
[ 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*
> Incremental deployment stopped working (at least for EAR)
> ---------------------------------------------------------
>
> Key: JBIDE-1231
> URL: http://jira.jboss.com/jira/browse/JBIDE-1231
> Project: JBoss Tools
> Issue Type: Bug
> Components: JBossAS
> Reporter: Max Andersen
> Assigned To: Rob Stryker
> Priority: Critical
> Fix For: 2.0.0.CR1
>
>
> Last nights build and current svn detects changes in files (the status changes to republish) but the files are actually not deployed!
> this is a *bad* regression ;(
--
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
More information about the jbosstools-issues
mailing list