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 102541

Summary:	Broken badge is not removed when reference is resolved
Product:	projects	Reporter:	Alexander Kouznetsov <mrkam>
Component:	Generic Projects UI	Assignee:	Milan Kubec <mkubec>
Status:	VERIFIED DUPLICATE
Severity:	blocker
Priority:	P2
Version:	6.x
Hardware:	PC
OS:	Windows XP
Issue Type:	DEFECT	Exception Reporter:
Attachments:	The project is created and the reference is broken The reference is resolved

Description Alexander Kouznetsov 2007-04-25 20:16:22 UTC

NetBeans IDE Dev (Build 070425)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251

Steps to reproduce:
- Create New Samples > Web > JSTL Example Application
- Since its target is Tomcat which is not registered in IDE, the dialog is shown
about this broken reference and the project icon is marked with asteric yellow
triangle mark
- Wait for scanning to complete. There is another badge is added to project's
icon: red square with a cross
- Now resolve broken reference: provide either GlassFish or Tomcat as the target
server
- RESULT: Yellow asteric badge is removed, but red square badge still persists.

I believe this is a REGRESSION. Could you please check this out.

There are also another steps:
- Open an Enterprise Project with broken dependency on another project (you
could try this one:
http://www.netbeans.org/nonav/issues/showattachment.cgi/38685/jboss_test.zip)
- Fix this dependency
- Obtain the same results: red square with a cross badge is not removed.

Comment 1 Alexander Kouznetsov 2007-04-25 20:17:49 UTC

Created attachment 41662 [details]
The project is created and the reference is broken

Comment 2 Alexander Kouznetsov 2007-04-25 20:20:08 UTC

Created attachment 41663 [details]
The reference is resolved

Comment 3 Jan Lahoda 2007-04-25 20:23:21 UTC

The "in error" badge is added by the Java Tasklist - it does not follow changes
in the classpath correctly yet.

*** This issue has been marked as a duplicate of 101281 ***

Comment 4 Alexander Kouznetsov 2007-04-25 20:29:13 UTC

Verified