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: | cross-cluster module patch jars | ||
|---|---|---|---|
| Product: | platform | Reporter: | Rich Unger <richunger> |
| Component: | Module System | Assignee: | Jaroslav Tulach <jtulach> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | jglick, rrochat |
| Priority: | P3 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
This issue had *2 votes* before move to platform component I usually advocate donating a source code patch to the affected API then hacking around it with patched JAR files. I am going to do that now and close as won'tfix. |
If I'm developing my own module suite and cluster, I'd like to be able to have a $cluster/modules/patches/org-netbeans-modules-foo/mypatch.jar, though the foo module is in enterprise2, ide5, etc. core/bootstrap/src/org/netbeans/StandardModule.java would need to be modified. Particularly the section referenced with the comment: // #9273: load any modules/patches/this-code-name/*.jar files first: It would need to loop through several patchdirs (one for each active cluster).