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.
Summary: | "Missing Library" resolution is unfriendly | ||
---|---|---|---|
Product: | java | Reporter: | jsight <jsight> |
Component: | Project | Assignee: | 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
Reassigning to "projects" for evaluation. May be duplicate. 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. For shared libs, see issue #44035, already prepared but did not make it into 6.0. Shared libs are already implemented, right? Can we close this issue? Milosi? jbecicka: not sure. While sharable libraries are there, there still can be unresolved library references. I personally do not believe that shared libs are the only thing needed here. The dialog really should be quite a bit more friendly. 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. Bug prior to 7.0, not touched for the last 2 years --> P4. 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. I will try to address it into NB 7.3. |