[jboss-jira] [JBoss JIRA] Resolved: (JBDEPLOY-207) Allow changing timestamp on a deployment root folder (blah.war) to redeploy

[Ales Justin (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBDEPLOY-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ales Justin resolved JBDEPLOY-207.
----------------------------------

    Resolution: Done


See DirModificationCheckerFilter usage in
http://anonsvn.jboss.org/repos/jbossas/projects/jboss-deployers/trunk/deployers-vfs/src/test/java/org/jboss/test/deployers/vfs/structure/modified/test/DirRemovalModificationTestCase.java


> Allow changing timestamp on a deployment root folder (blah.war) to redeploy
> ---------------------------------------------------------------------------
>
>                 Key: JBDEPLOY-207
>                 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-207
>             Project: JBoss Deployers
>          Issue Type: Feature Request
>          Components: maindeployer
>            Reporter: Rob Stryker
>            Assignee: Ales Justin
>             Fix For:  JBDEPLOY-2.1.0.Alpha1
>
>
> If I execute the following, JBoss 5.1 doesn't redeploy a module even though its clearly new. (assuming the module has no descriptor file required)
> cd server/default/deploy
> rm -rf some.war &&  cp -R /home/rob/tmp/some.war .
> Clearly the entire project was removed and a new version coppied over, however the server has not recognized it as new because there is no descriptor. 

-- 
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