Bug 207001 - Cleaner way of conditionally enabling development-build-only UI
Cleaner way of conditionally enabling development-build-only UI
Status: NEW
Product: www
Classification: Unclassified
Component: Builds & Repositories
7.1
All All
: P3 (vote)
: TBD
Assigned To: pgebauer
nbre
issue_reviewed
: ARCH, NO72
Depends on:
Blocks: 206954
  Show dependency treegraph
 
Reported: 2012-01-06 19:28 UTC by Jesse Glick
Modified: 2012-06-13 12:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2012-01-06 19:28:29 UTC
Some modules or features, such as java.debug and timers, are mainly intended for NB developers and QE to explore the IDE's features. (Some like apisupport.projectinspector fall into this category but are currently on AU.) Currently these are either removed from their cluster config in release branches, which is awkward since you need to keep track of them all; or conditionally enable certain features based on whether assertions are on or off, which overloads -ea to affect UI, and make use of lazy registration annotations impossible.

Possible solutions:

1. Move these modules to Stable AU and let anyone who wants to use them download them that way. Simplest and clearest, though might be annoying if most dev build users want these things on.

2. Make them deps of some kit module in the nb cluster, all disabled by default; you could then enable them in Plugin Manager. Straightforward but means that this kit module must depend on some domain-specific modules like java.debug.

3. Make them eager modules requiring some token which is provided by a module which is disabled or missing by default. Solves the dependency problem of #3.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo