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 249293 - remove standard modules from nbms-and-javadoc
Summary: remove standard modules from nbms-and-javadoc
Status: NEW
Alias: None
Product: updatecenters
Classification: Unclassified
Component: Dev (show other bugs)
Version: 8.1
Hardware: Other Linux
: P2 normal (vote)
Assignee: pgebauer
Depends on:
Reported: 2014-12-11 12:39 UTC by Jaroslav Tulach
Modified: 2015-11-06 11:30 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2014-12-11 12:39:21 UTC
Having only extra modules on its AU would prevent issues with version mischmash...
Comment 1 Jaroslav Tulach 2014-12-19 11:12:40 UTC
People often add nbms-and-javadoc AU catalog into previously released versions of the IDE just to get an extra module. However together with their module they also get tons of updates of released modules. Nobody tests for compatibility between previous release and dev build and as such this is causing enormous problems.

However, if we the nbms-and-javadoc catalog contained only extra modules (contrib, extra, etc.), the problems with updates might be gone. Uses of NetBeans 8.0.x would never get development version of masterfs (for example) through this catalog. So the suggestion is to split the nbms-and-javadoc catalog into two and keep just add-ons on the original location. Have the catalog for regular modules at nbms-and-javadoc more hidden and referenced only from dev build.

=== Plugin Portal Catalog in Dev Build ===

For similar reasons (e.g. get extra functionality) people include plugins AU catalog in dev builds. Imho, it should be there by default and point to latest previously released version. In general running modules built against previous binaries in new version should work (unless their versions properly identify they are incompatible) and having them included in dev build will at least notify us early about potential incompatible changes.
Comment 2 Antonin Nebuzelsky 2015-11-06 11:29:44 UTC
Let's plan on doing in trunk now.

Petr, have a look at implementing this. Thanks.