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.

Bug 75937 - Provide friend API from apisupport for NBM project template wizards
Summary: Provide friend API from apisupport for NBM project template wizards
Status: RESOLVED WONTFIX
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: API
Depends on:
Blocks:
 
Reported: 2006-05-04 15:46 UTC by _ tball
Modified: 2011-11-21 14:35 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ tball 2006-05-04 15:46:43 UTC
Jackpot currently adds Java class templates for NetBeans module projects.  In
the future we would like to instead use a wizard which also defines the class's
layer.xml registration.  The apisupport modules has very useful classes to do
this, such as CreatedModifiedFiles and LayerUtils, but these are not public. 
Please consider making this functionality available so that other modules can
define new content wizards for NetBeans modules.
Comment 1 _ tball 2006-05-04 16:08:33 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.
Comment 2 Jesse Glick 2006-05-04 17:22:46 UTC
"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.
Comment 3 _ tball 2006-05-04 17:39:47 UTC
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.
Comment 4 Jesse Glick 2008-02-20 22:23:35 UTC
I just looked for the templates you mentioned but could not find them. Is this issue still valid?
Comment 5 Jesse Glick 2011-11-21 14:35:11 UTC
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.