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 211526 - Installing JUnit doesn't show in library list until restarted
Summary: Installing JUnit doesn't show in library list until restarted
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 7.2
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-20 16:26 UTC by javydreamercsw
Modified: 2012-04-25 19:00 UTC (History)
1 user (show)

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 javydreamercsw 2012-04-20 16:26:50 UTC
Product Version = NetBeans IDE Dev (Build 201204200400)
Operating System = Windows 7 version 6.1 running on x86
Java; VM; Vendor = 1.7.0_03
Runtime = Java HotSpot(TM) Client VM 22.1-b02

The JUnit is not available to be added unless IDE is restarted but it is not required to (plug-in setting)

To reproduce:
1) Start with an IDE without JUnit installed (don't install when prompted during install/start up)
2) Open/Create a java project
3) Right click on Test Libraries>add library
4) Verify the JUnit library is not listed
5) Install JUnit plug-in (in my case is set up to be in shared dir)
6) After install notice you are not prompted to restart IDE.
7) Right click on Test Libraries>add library
8) Notice the JUnit library is not listed (should be at this point)
9) Re-start IDE
10) Right click on Test Libraries>add library
11) Verify the JUnit library is listed

It might be as easy to mark the plug-in to request restart.
Comment 1 Jesse Glick 2012-04-25 16:24:26 UTC
(In reply to comment #0)
> 7) Right click on Test Libraries>add library
> 8) Notice the JUnit library is not listed (should be at this point)

Is it in Tools > Libraries or not?
Comment 2 javydreamercsw 2012-04-25 17:55:22 UTC
I tried the scenario on Build 201204250400 and everything worked fine. Maybe a transient error?
Comment 3 Tomas Zezula 2012-04-25 19:00:50 UTC
Maybe the @OnStart problem.