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.
It appears that the alpha update center (http://www.netbeans.org/updates/dev_1.18_.xml) has not been updated since April 6th. The daily au_nbms bundle has the latest auto update modules, so something is broken posting them to the website for auto update distribution.
I'll take a look at it.
Automated updating script was heavily dependent on text formating of NBM's Info/info.xml file and I guess it got broken with change in MakeNBM task which recently started using xmlutil.write(). I've updated the script to be 'less' dependent on formatting, repopulated the Update Center and it looks fine for me.
Yep - I'm now downloading the latest Jackpot and Metrics (I never knew the latter was updated!) Cheers ;-)
Where is this updating script? Infrastructure like this should be in nbbuild.netbeans.org, I think. Re. "less" sensitive to formatting - why is it sensitive at all? Should be using an XML parser. nbbuild/antsrc/org/netbeans/nbbuild/MakeUpdateDesc.java does do some string outputting for the XML header because AFAIK DOM does not support writing entity includes (I think this is corrected in DOM-3 in JDK 6).
Jesse, the updating script is a piece of shell script in closed source repository. The script gets respective values using grep, cut, awk and perl utilities. Certainly not using XML parser. I'm not that certain about any infrastructures that automatically maintain /download space and very specific "web pages" (Update Centers) should be in nbbuild.netbeans.org. Underlying Ant task MakeUpdateDesc is already there. I can imagine one more task put into opensource, but certainly not details about /download space maintenance. I'm not against providing some generic tool for maintaining update center, but the script is not that generic. Maybe Michal would consider this in his tooling efforts. I'll do just maintenance of the existing script as I'm moving to another project.
I guess I don't see what is done that <makeupdatedesc> doesn't already do, but if the publishing stuff is currently shell scripts then never mind - can't be fixed easily.
mekeupdatedesc works with NBMs, which were somehow pre-identified via filesets and groups for filesets. The shell script does maintenance of local cache of NBMs comparing it against freshly built NBMs. Fresh NBM can get into local cache under following conditions (OR relation): - "old" NBM file in cache is more than 14 days old, so the "old" file is deleted from cache and next condition comes into action - NBM does not exist in the cache - NBM in cache has different specification version This way it assures no ancient (and incompatible) NBMs persist in cache for months, while it helps prevent disappearance from Update Center when temporary build/compilation issues occur. New build.xml is generated from following metadata from NBMs in cache: - OpenIDE-Module-Display-Category - NBM filename The build.xml is then executed, new NBMs uploaded to website and Update Center Catalog pushed live. The task I can imagine to be put into nbbuild is the management of local NBM cache.
Yes, NBM management could be a task. But <createupdatedesc> could also be enhanced to autocreate groups from module display categories - would be straightforward I think.