While installing the new eclipse indigo IDE I\'ve tried to setup the tomcat server previously downloaded from Apache web site (tomcat 7.0.20) with no success. When I fill th
Eclipse can't use an installed copy, and that's what it sounds like you've got. Installed copies usually have their libraries and configuration files scattered in unpredictable ways that make it difficult/impossible for Eclipse to properly launch the server itself. You may not need 7.0.12, but you will need to use the zip/tar.gz download.
Launch eclipse, goto Window / Preferences / Server / Runtime and add Tomcat installation directory. This registers Tomcat with Eclipse Indigo.
It seems that there is no Helios version for Mac, only Indigo.
I've downloaded Eclipse for Java EE developers (Eclipse Indigo 64 bit, running JDK 1.6.0_25 64 bit) and I've successfully added Tomcat 7.0.20 as a server (and Tomcat 7.0 for Windows). Unless you specify the error logs, there is no problem whatsoever.
I think the invalid version message is a bit misleading; it just doesn't like something about the installation. Anyway, here's what worked for me, using Ubuntu 11.10, eclipse Indigo JavaEE SR2, tomcat 7.0.21.
I have a standalone tomcat installation as per the standard ubuntu tomcat7 package. I used tomcat7-instance-create to create a separate tomcat instance for eclipse:
$ tomcat7-instance-create -p 8000 -c 8003 ~/dev/eclipse/tomcat
This required a few additions to keep eclipse happy
$ cd ~/dev/eclipse/tomcat
$ ln -s /usr/share/tomcat7/lib
$ ln -s /var/lib/tomcat7/conf/policy.d/03catalina.policy conf/catalina.policy
$ ln -s /usr/share/tomcat7/bin/bootstrap.jar bin/bootstrap.jar
$ ln -s /usr/share/tomcat7/bin/tomcat-juli.jar bin/tomcat-juli.jar
$ tree
.
├── bin
│ ├── bootstrap.jar -> /usr/share/tomcat7/bin/bootstrap.jar
│ ├── setenv.sh
│ ├── shutdown.sh
│ ├── startup.sh
│ └── tomcat-juli.jar -> /usr/share/tomcat7/bin/tomcat-juli.jar
├── conf
│ ├── catalina.policy -> /var/lib/tomcat7/conf/policy.d/03catalina.policy
│ ├── catalina.properties
│ ├── context.xml
│ ├── logging.properties
│ ├── server.xml
│ ├── tomcat-users.xml
│ └── web.xml
├── lib -> /usr/share/tomcat7/lib
├── logs
├── temp
├── webapps
└── work
Then just add a new runtime environment and server as normal, and it's all good!
HTH,
Following on the advice to add some symbolic links, I needed to due the following to match my synaptic tomcat7 /usr/share/tomcat7 to eclipse indigo's requirements.
Install tomcat7 using synaptic. Add a tomcat7 server using the eclipse wizard (I let eclipse download it into /home/me/tomcat7 ). Compare the folder structure of /usr/share/tomcat7 and /home/me/tomcat7. Add any symbolic links from /var/lib/tomcat7 to /usr/share/tomcat7 to match /home/tomcat7 . Copy the 'missing' jars in /home/me/tomcat7/bin and /home/me/tomcat7/lib to their respective locations in /usr/share/tomcat7 .
In short - let the wizard setup the server, then see what you can do to adulterate your synaptic configuration to match the eclipse needs ;-) Worked for me in Ubuntu 12.04 oracle java 1.7.
I found this page amazingly helpful
Tomcat 7 with Eclipse
Also a lot of my problems went away when I switched from Elipse Classic to Eclipse Java EE IDE for Web Developers.