|
||||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||||
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-Depend... Andreas Zoike (JIRA)
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-D... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-D... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-D... Andreas Zoike (JIRA)
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-D... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-D... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-D... Andreas Zoike (JIRA)
- [mojo-dev] [jira] (MNBMODULE-184) System-Scope-D... Milos Kleint (JIRA)

I believe your workaround is the correct solution to your problem. There are many valid cases when tools.jar has to be present on module's classpath but in most cases it's not to be included in the module. Quite the opposite, it could prove counter productive.
The typical way of adding dependency on jdk instead of jde is described here:
http://bits.netbeans.org/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/api.html
OpenIDE-Module-Package-Dependencies entry.
example code is here:http://hg.netbeans.org/main?cmd=changeset;node=24499d81bb5c