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 91036

Summary: "Missing Library" resolution is unfriendly
Product: java Reporter: jsight <jsight>
Component: ProjectAssignee: Tomas Zezula <tzezula>
Status: NEW ---    
Severity: blocker CC: bleonard, dbotterill, gsporar, mkleint, musilt2, olangr
Priority: P3 Keywords: UI
Version: 5.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description jsight 2006-12-13 19:51:09 UTC
The missing library dialog should give you clearer options for how to resolve
the issue.

Some logical options would be:
1. Remove the library reference (my option for the case that prompted this
report, as the library reference was obsolete anyway)
2. Create a new library reference (avoids typos, and avoids us having to realize
that the library name is case-sensitive (not sure why it is case sensitive
either, really)
3. Manage Libraries - For those who want the current, expert only option
Comment 1 Peter Pis 2006-12-14 08:38:57 UTC
Reassigning to "projects" for evaluation.
Comment 2 Jesse Glick 2006-12-14 14:47:15 UTC
May be duplicate.
Comment 3 David Botterill 2007-09-13 13:06:56 UTC
I totally agree on this one.  I just manned a booth at Boston NB Day and many developers have problems with library
references in a team environment.  If a library reference is defined, we should show them what is in the library and let
them define the reference finding the necessary jars.

Ideally we should define a "shared" library reference that lives with the project.  I know namespace other issues would
need to be addressed but this might also allow projects to be more portable.
Comment 4 Jesse Glick 2007-09-17 04:40:59 UTC
For shared libs, see issue #44035, already prepared but did not make it into 6.0.
Comment 5 Jan Becicka 2008-02-18 15:40:13 UTC
Shared libs are already implemented, right? Can we close this issue? Milosi?
Comment 6 Milos Kleint 2008-02-18 18:32:33 UTC
jbecicka: not sure. While sharable libraries are there, there still can be unresolved library references.
Comment 7 jsight 2008-02-19 01:22:41 UTC
I personally do not believe that shared libs are the only thing needed here.  The dialog really should be quite a bit 
more friendly.
Comment 8 Sergey Petrov 2009-04-14 11:14:16 UTC
reproducible with 6.7m3, don't see how to remove unresolved reference for example.
But it's nt necessary to replace reference with exactly the same jar, so may be  #2 was fixed.
Not sure what #3 means, but dialog do not allow anything except resolve reference.
Comment 9 David Strupl 2012-10-25 13:41:53 UTC
Bug prior to 7.0, not touched for the last 2 years --> P4.
Comment 10 Tomas Zezula 2012-10-26 06:46:50 UTC
IN NB 7.3 a API was created which allows modules to supply code and UI for resolving project problems (ProjectProblemsProvider). Now only the UI has to be designed.
Comment 11 Tomas Zezula 2012-10-26 06:48:45 UTC
I will try to address it into NB 7.3.