Bug 134338 - Unable to add Tomcat5 as a Runtime Server in Eclipse 3.1 JST 0.7
Summary: Unable to add Tomcat5 as a Runtime Server in Eclipse 3.1 JST 0.7
Status: RESOLVED FIXED
: 153470 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Java (show other bugs)
Version: RC 4
Hardware: i586 SuSE Linux 10.0
: P5 - None : Major
Target Milestone: ---
Assignee: Daniel Bornkessel
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-17 23:40 UTC by Gordon Mathis
Modified: 2006-03-20 19:38 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Mathis 2005-11-17 23:40:27 UTC
I am able to install Tomcat5 through Yast and it seams to work fine. However, when I select that Tomcat installation in eclipse as a Runtime Server. It gives the error message
"The Tomcat installation directory is not correct. It does not point to a valid Tomcat installation."
This happens because of the way Tomcat is spread across several directories and use symbolics links.  
This link (http://www.eclipsezone.com/eclipse/forums/t33013.html) gives more details of the problem and even a fix to get around the install problem. I tried fix and I got it to install, but it failed when I tried to run a sample servlet. If I just download Tomcat5.5 from www.apache.org everything works great.
Comment 1 Daniel Bornkessel 2006-01-31 16:44:51 UTC
Links are fixed now.
Testing now how to be able to use our Tomcat with eclipse.
Comment 2 Daniel Bornkessel 2006-03-01 10:32:28 UTC
*** Bug 153470 has been marked as a duplicate of this bug. ***
Comment 3 Marc collin 2006-03-01 15:09:31 UTC
i have also this problem
Comment 4 Daniel Bornkessel 2006-03-20 19:38:37 UTC
Works with current packages (SUSE10.1Beta8). 
Instructions can be found at
http://en.opensuse.org/Java/tomcat5
Feedback is very welcome.
... closing bug as resolved.