For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 1 reply, 2 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
Development Environment:
Tomcat 5.5.7
Eclipse 3.01
MyEclipse 3.8.4
Windows 2000 ProWhile upgrading from Tomcat 5.0.28 to the new Tomcat 5.5.7 stable release I encountered the dreaded undeployment failure problem in MyEclipse. Having followed the development of 5.5.x and read many posts on JAR locking issues, I immediately changed the Tomcat locking settings in server.xml. As the Tomcat docs indicate, there was a significant increase in startup time but the redeploy problem did not go away.
Anyway, after some more poking around on google, I found a post that mentioned setting the Tomcat “working path” from the Tomcat Monitor. This fixed the redeploy problem but only when I start the Tomcat service from outside of MyEclipse. My question is how to get MyEclipse to start Tomcat the same as the standard tomcat service launcher?
BTW – Here is the link I mentioned above:
http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg145238.html
David,
If the working path can be set by an environment variable to the VM (-Dsomething) then you can add it to the option VM args field of the connector. If the working path is set by changing a file, then it likely cannot be changed within MyEclipse. This is one of the reasons we added full debugging for remote/running servers, incase people had to start their servers outside of MyEclipse, so you can make use of this functionality in the case that you can’t get Tomcat starting inside of MyEclipse.
