[ https://issues.jboss.org/browse/JBIDE-10449?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-10449. ----------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10449?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-10449 at 4/25/12 8:58 AM: ---------------------------------------------------------------- It should now be possible to only do a full redeploy based on the reg exp. But sometimes it doesn't work. Sometimes when you set a new reg exp, save it and restart the server, the old pattern is still used. This should reproduce it: 1. Set up AS 7.1.1 server 2. Create Dynamic Web Project dynproj 3. Add index.jsp and home.jsp in WebContents of your project 4. In Server View open the server in server editor 5. In Application Reload Behavior check "Customize application reload..." 6. In Application Reload Behavior change the pattern to \.jsp$ - this will ensure that every change in jsp files forces full publish - save the server editor 7. Start the server and deploy dynproj 8. Change home.jsp and save - in a few seconds you will see JBAS018565: Replaced deployment "dynproj.war" with deployment "dynproj.war" in the Console 9. Change index.jsp and save - you will see the same as in step 8. 10. Stop the server 11. Change the pattern in server editor to index\.jsp$ - only changes in the index.jsp should force full publish - save the editor 12. repeat steps 7.-9. - in both cases the file change will cause full publish which is wrong - FAIL was (Author: mmalina): It should now be possible to only do a full redeploy based on the reg exp. But whatever you set as the pattern, full redeploy happens any time I update a jsp and save it. 1. Set up EAP 6 ER5 2. Create a simple dynamic web project 3. Create index.jsp in the WebContents of your project 4. Start the server and deploy your project 5. Change something in the jsp and save it 6. In server log you will see something like "Replaced deployment "dynproj.war"" - FAIL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10449?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-10449. --------------------------------- Resolution: Done This general issue was fixed for b1, and I won't change the fix version. Please open a new jira with the caching issue bug for cr1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira