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: | Provide friend API from apisupport for NBM project template wizards | ||
---|---|---|---|
Product: | apisupport | Reporter: | _ tball <tball> |
Component: | Project | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | Keywords: | API |
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ tball
2006-05-04 15:46:43 UTC
A friend API is a good start (and all Jackpot needs), but my understanding is that apisupport's friends have to be defined within its project.xml file. This prevents other modules from benefiting from this useful functionality. Maybe there is less interest in such a feature than I think, however. "apisupport's friends have to be defined within its project.xml file" - yes of course. "This prevents other modules from benefiting from this useful functionality" - unless they ask for it and are added as friends. The whole point of a friend API is that you are not prepared to produce something stable enough for universal use and permanent compatibility, so you want to have your clients enumerated so you can plan incompatible changes. I understand the issues and support your desire to not make a private API public just because someone is interested in it. Tuning these classes to be publicly supportable requires additional work which is a much lower priority than other tasks in your team's queue. Thank you for allowing Jackpot "early access" to some very nice technology. I just looked for the templates you mentioned but could not find them. Is this issue still valid? Possibly obsolete. Anyway new APIs generally use Java annotations to register objects, which removes most of the need for special IDE support when creating from template; apisupport typically adds module dependencies for you as a convenience. |