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: | Wrong class-path property in manifest | ||
---|---|---|---|
Product: | java | Reporter: | Jiri Prox <jiriprox> |
Component: | Project | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | tjquinn |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jiri Prox
2006-12-15 12:43:12 UTC
The ending / is not needed. Reopening We do not support copying of lib folders anyway. Decreasing priority. moving opened issues from TM <= 6.1 to TM=Dev Just a little more data on this. NB seems to do something to manage the class path correctly if I: - write an app to use getResource intending to locate a file in a library directory, - add a directory via the library dialog, - place a file in that directory, and - run the app from inside NB (at least in 6.7 RC 2). As noted earlier the generated manifest contains Class-Path: lib/extrastuff But when I try to run from outside NB using "java -jar ..." the program cannot find that resource. If, though, I manually hack the manifest to add the trailing slash to lib/extrastuff in the Class-Path then the app runs successfully from outside NB as well. It seems that the trailing slash is indeed required for Java to do the right thing outside NB, and it's too bad that the app behaves differently when I run from NB. In light of these facts I think this merits a P3 priority. Agree? This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss |