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: | Problem when resolve dependencies | ||
|---|---|---|---|
| Product: | java | Reporter: | ankor <ankor> |
| Component: | Project | Assignee: | Tomas Zezula <tzezula> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | P4 | ||
| Version: | 7.2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
ankor
2012-05-31 08:02:06 UTC
After installation i opened a old project. In this project are libraries over the library-manager connected. A wizard told me, that i must resolve these dependencies, so i will do. For resolving i must create a new Library named "JDateChooser". But i do wrong, i wrote "JDateChoose" for the library-name. After i clicked "OK" the yellow dot says me, that i have make a mistake. I look and see my mistake, so i entered the lib-manger after clicking the resolve-button again, and change the name of the library. But this doesn´t resolve the problem. I only can resolve this by deleting the library and apply the lib with the correct name again. The problem is, that the resolve-wizzard doesn´t realise, that the correct lib-name is entered. In fact the resolve wizzard cannot realize it as the library with updated display name is not the same. The library has 2 names: The display name which can be changed and can contain spaces and non ant characters. The ant name which represents the library in ant files. This name is assigned to library when it's created and cannot be changed. Making it changeable will brake existing projects using the library when you change it. It will cause more problems than benefit. The solution is improve the resolve broken references to let you just point to jar(s), sources and javadoc and create correctly named library instead of letting you to manually do it. There is a request to improve the broken reference support: issue #123464. *** This bug has been marked as a duplicate of bug 123464 *** |