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.

Bug 187927 - Remove Server is faulty
Summary: Remove Server is faulty
Status: RESOLVED DUPLICATE of bug 187032
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 09:00 UTC by _ proxity
Modified: 2011-01-03 10:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ proxity 2010-06-22 09:00:27 UTC
I installed 6.9 and imported my settings from 6.8.
Then I used Tools/Servers to remove tomcat 6.0.20 to be sure that no stale references are hanging around when I uninstall NetBeans 6.8 and tomcat 6.0.20.

tomcat 6.0.20 is no longer visible in Tools/Servers but it wasn't removed from my web projects! Instead all of them had an empty choice in Project Properties/Run/Server. I didn't know that and tried to start my main project. That lead to a lot of error messages because my ordinary user couldn't write into the tomcat installation directory. After setting the server for the project manually to the current tomcat 6.0.26 the user writable ~/.netbeans/6.9/apache-tomcat-6.0.26_base/ was created. The project runs now, but there is still the possibility to select the empty entry in Project Properties/Run/Server.

I remember that older versions of the IDE displayed a exclamation mark on the project icon together with a Resolve Server Problem menu item in the context menu.

NetBeans also complains about missing write permissions for the Glassfish installation directory. I fact I never used Glassfish for my projects. I only installed it together with the IDE.
Comment 1 Petr Hejl 2010-10-12 14:14:49 UTC
This could be related to bug 187032.
Comment 2 Petr Hejl 2011-01-03 10:25:11 UTC

*** This bug has been marked as a duplicate of bug 187032 ***