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.
The only thing that is built daily and weekly is the stuff included in the standard distribution. I suggest that this is extended to 2 more categories: 1) stable modules (those that are stable and made available on AU, but not part of the distribution) - e.g. CORBA, Object Browser, DB Explorer,... 2) experimental modules - only those that would succesfully build would be included Those would be two other ZIP files aside from the main build, and should be available from the download page.
I think this is in the works, is it Robert?
Ping. This issue seems to be stalled somewhere, there has been zero activity for more than a half year, raising priority to P2.
This issue seems to be a duplicate of issue 22922.
It is related to 22922. This issue is mainly focused on what the "stable" distribution is. Currently the user can download stable release, but has to rely on AU to download additional "stable" stuff. Suggest to build all NBM marked as stable and make them available aside the main release installers (and daily builds) in a ZIP file with instructions on how to install.
Ian, actually on download page there are nbms packages with almost all buildable modules. There's no separation to "stable" modules and "all buildable" modules. There's no documentation what to do with nbms packages.
What is the status of this?
This doesn't seem to be so related to AU. =>reassigning to Ruda. It seems to be also somehow addressed (if not resolved). >There's no separation to "stable" modules and "all buildable" modules. I this still an issue? If so, the separation can be simply based on the information in which AU the modules are. > There's no documentation what to do with nbms packages. These should be probably just linked from development builds page. It seems to be done already (nbm-zip). Isn't it?
Ian, actual dev builds goes with two kinds of NBMs packages. ide-nbms-* and au-nbms-*. Do you want to divide au-nbms-* to say stable-au-nbms-* and experimental-au_nbms-* ? I would like to say, that this separation doesn't imply the user will save download time. I would expect the user will allways download experimental modules.
Wow, only year and half passed, and we are starting to see the light at the end of the tunnel ? (are we?) I do not understand at all why it is so hard to understand this request. So let me try once again: The user of NetBeans IDE goes to http://www.netbeans.org/downloads/ide/index.html and picks the IDE installation for his platform. As part of the installation, he gets the set of modules we call "standard distribution". Currently, there is no way for this user to also download the other "stable" set of add-ons available for this particular version of IDE (e.g. to burn on CD and bring home, where he has no internet connectivity). By "stable" I meant the set of modules I would see if I would install this IDE and connect it to the NetBeans stable update center. I am requesting that the content of stable update center is also packaged and made available for download at the http://www.netbeans.org/downloads/ide/index.html page. Obviously (I hope), the dev builds do NOT solve this issue. If this is still unclear please call me, or come to see me, or just close this issue as INVALID, or what the hell is the right state for things that are filed by someone as weird as me.
Ian, I've divided current dev builds AU NBMs package into two packages. These packages are "Alpha" and "Stable". BTW:Jack maintains certain facility preparing the page http://www.netbeans.org/catalogue/ . Updating that facility to prepare such a package on daily basis would be easy (download referenced NBMs, pack them, upload back, update metadata in database). It seems to be morethanless website management task. Jack would you comment on this?
Funny, I requested the same thing in issue 20716, in Feb 2002. That issue unfortunately somehow morphed into just listing the modules included in the standard distribution with links to their sites. Rudo - yes I can do this, of course, but it seems to me this should be part of a build process, whenever new nbms are built and distributed to AU. If you disagree, re-assign this issue to me and I will go ahead and do it on my side, as you described.
I am patching ${config.modules.stable-au} after the build system merge; someone please review the new list.
I think this is not longer an issue