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.
Add an "Attic" tab to the plugin center (Tools | Plugins) to display legacy applications that are in the build process but are no longer being developed, maintained or tested. This feature can cause unwanted bloat and instability to the IDE so perhaps it should be installed as a separate module or better yet, selectable at install time (same as Tomcat and Glassfish are selectable in the installation wizard). Benefits: In addition to letting users have access to modules which they may have been using in previous versions of the IDE, the feature will provide a quick look for modules/plugins that are no longer supported (end-of-life) or are on indefinite hold. Option 2: Tools | Attic Plugins Thanks.
Related to this, we may want to have a separate source code repository that would contain the attic plugins, so they don't bloat the main repository.
CC'ing myself, this seems a sane idea.
Idea seems to be taking... thanks to Kristian Rink for planting the seed. Note: Here is Kritian Rink's initial e-mail response to a question on Woodstock. He suggestis an Attic Update Center for non-active technologies: "Well... Adding to this, indeed I would like to see, well, sort of a "collected" list of technologies / frameworks eventually included in / supported by NetBeans plugin and their current state of life or development. This includes Woodstock, but also things like jMaki, Phobos, ... which used to be around for quite a while but (looking at their project sites) seem pretty dead as of lately. Maybe for modules like that it would generally be helpful to have, well, something like an "attic Update Center", to identify modules which are there (and eventually updated for recent NetBeans builds) despite the fact that the technologies they are based upon aren't actively developed anymore?"
Well... could have copied this mail here myself, indeed. :)
No need for a separate tab. The PM GUI already lets you have several UCs registered, each with their own icon - we use to mark beta modules, for example. So this would be of similar stability level to beta, but for a different reason - used to be stable, now maybe not so much.