-
Feature Request
-
Resolution: Done
-
Major
-
3.3.0.Beta1
-
None
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
- is cloned by
-
JBIDE-10449 [api] force PublishCopyUtil to use a server behaviour's logic to restart modules when certain files have changed
-
- Closed
-