tomcat7-instance-create instances not compatible with Eclipse

Bug #1195189 reported by David Edwards
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
tomcat7 (Ubuntu)
Low
Unassigned
tomcat8 (Ubuntu)
Undecided
Unassigned

Bug Description

If you create a private instance of Tomcat 6 using the tomcat6-instance-create script, it can be used as a Tomcat 6 server in Eclipse by creating a new server runtime environment that has its installation directory set to be your private instance directory.

However, the same is not true for tomcat7-instance-create; Eclipse cannot find the files normally in lib/, bootstrap.jar, and catalina.policy.

There was a bug raised for Tomcat 6 (https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/297675) which was fixed by a patch that sets up the missing files in the private instance. It would be ideal if the same could be done for Tomcat 7.

See also:
http://askubuntu.com/questions/313103/cannot-start-tomcat-after-installing-a-private-instance

Changed in tomcat7 (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tomcat7 (Ubuntu):
status: New → Confirmed
Revision history for this message
Thiago Dourado de Andrade (7hi4g0) wrote :

Testing here, Eclipse reconized the instance when I created a symbolic link to the lib/ path.
Maybe just adding the link to skel/ should solve it.

Revision history for this message
Thiago Dourado de Andrade (7hi4g0) wrote :

Just to note. The private instance is not compatible with Sysdeo Tomcat plugin also.

Revision history for this message
Nish Aravamudan (nacc) wrote :

As far as I can tell, this probably needs to be filed as bug(s) in Debian, much like the tomcat6 change. Would you be willing to file them?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers