- This topic has 3 replies, 2 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
Seems like the semi-hot deployment on 5.0 got broken in this build.
Changes made to jsp’s no longer are automatically deployed to my jboss deploy directory.
have to shut down jboss, manually deploy and restart jboss. If I deploy while jboss is running, I get an “out of date” warning.thx
I can’t rperoduce this. I installed Eclipse 3.2RC5 and MyEclipse 5.0M1 clean install, configured them with JBoss 4.0.2 and deployed a test project with an exploded deployment (make sure you are using exploded). As I made changes to the JSP and saved it and went back to my browser to refresh, I saw the changes. I also checked the deployment tool and the project was not out of date.
Are you running a script to update any files in your project? That *will* cause out of date warnings.
When you create your deployment (using the toolbar button as outlined in our app server doc here: http://www.myeclipseide.com/images/tutorials/quickstarts/appservers/) you specify what kind of deployment. If you are using File > Export, that would explain why things aren’t going smoothly.
