This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 200710020000 ] [ JDK VERSION : 1.6.0_02 ] The latest daily build of NetBeans correctly decided to upgrade tomcat from 6.0.13, as installed by NB 6.0 beta 1, to 6.0.14. However, I lost the VM options property as defined under the platform tab. My web application would not start without it. Upgraded tomcats should inherit the settings of earlier versions, particularly if it is only a patch upgrade.
what specifically should be done? it is not clear from the message. where is the information stored? How should the installer "inherit the settings of earlier versions"? Isn`t it the tomcat module issue?
Anyway.. not a defect but the enhancement.
In NB beta 1 under the tomcat properties I setting the VM options. I then upgraded NB, which as a consequence upgraded tomcat and lost those VM options. In other words the installation has treated the minor upgrade of tomcat as a new install. However, the old tomcat is not available, which implies otherwise. It should be treated as an upgrade - this is what the user will expect. This could lead the unwary user to experience what seem to be bugs in their code or to miss bugs in their code because tomcat is no longer how they had set it up. A tomcat server should have the same properties after upgrade as it does before. Failing this the user should be given the tomcat in addition to rather than instead of the old tomcat.
dynamite, to clarify the way of tomcat registration in netbeans: http://wiki.netbeans.org/wiki/view/TomcatAutoRegistration The first time we install netbeans IDE we add ...catalinaHome and ...token to the netbeans_default_options in etc/ netbeans.conf. When we install the new version of tomcat, we modify catalinaHome and token to pickup the just installed tomcat. thanks, Dmitry