- This topic has 9 replies, 3 voices, and was last updated 20 years ago by bradm.
-
AuthorPosts
-
bradmMemberI have followed the installation instructions to the letter, and I still cannot start or stop Tomcat from within MyEclipse. The error is clear: “Java Virtual Machine Launcher: could not find the main class”. I have pointed to the root of my full 1.5 sdk as per the instructions though, so I’m not clear as to what the problem could be.
Riyad KallaMemberbradm, please let me know what version of Eclipse/MyEclipse you are running AND your settings for all of the TOmcat 5 connector fields.
bradmMemberSorry: My Eclipse 3.8.4; Eclipse 3.01; Tomcat home is C:\Program Files\Apache Software Foundation\Tomcat 5.5\; JRE Home directory is C:\Program Files\Java\j2sdk1.5.0.
Robert VargaParticipantYou should probably try Eclipse 3.1m4 for launching Tomcat 5.5 (or configuring Tomcat 5.5 for Java1.4, see Tomcat 5.5 readme for this), since probably the debug protocol is incompatible between Eclipse3.0 (which supports only Java1.4) and Java5.
Regards,
Robert
Riyad KallaMemberhmm, good suggestion Robert. Bradm can you confirm/deny what Robert is suggesting by doing a parallel setup of Eclipse 3.1M4 and MyEclipse 3.8.4 Beta for Eclipse 3.1M4?
bradmMemberThanks: Can I simply replace my current Eclipse installation with 3.1M4, or will I need to reinstall MyEclipse too?
Riyad KallaMemberBecause the MyEclipse version for 3.1M4 is actually a separate download, you will need to reinstall both.
Robert VargaParticipantI suggest you use the manual install versions, that way different versions of ME surely won’t mess with each other in Windows registry (I don’t know whether they do otherwise, but it is simpler that way).
So have a different Eclipse install for 3.0.x and a separate one for Eclipse 3.1.y, and use 3.8.4 for 3.0.1 and use 3.8.4-for-3.1M4-Beta for 3.1M4, both installed manually. I don’t have any problem this way.
Oh, and make sure to use separate workspaces, because if a workspace is converted for 3.1M4, it will most probably not function in 3.0.x.
Regards,
Robert
Riyad KallaMember(I don’t know whether they do otherwise, but it is simpler that way).
The installer may write InstallShield-specific values to the registry, but we don’t write any values there.
So have a different Eclipse install for 3.0.x and a separate one for Eclipse 3.1.y, and use 3.8.4 for 3.0.1 and use 3.8.4-for-3.1M4-Beta for 3.1M4, both installed manually. I don’t have any problem this way.
Oh, and make sure to use separate workspaces, because if a workspace is converted for 3.1M4, it will most probably not function in 3.0.x.
Robert’s suggestion is a good one and how most of us work around here.
bradmMemberThanks all. I followed all the suggestions above and everything is right with the world! Ciao.
-
AuthorPosts