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 207075 - Update center omits OSGi bundles
Summary: Update center omits OSGi bundles
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal with 2 votes (vote)
Assignee: pgebauer
: 209119 (view as bug list)
Depends on:
Reported: 2012-01-09 17:10 UTC by Jesse Glick
Modified: 2014-02-16 11:23 UTC (History)
6 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 Jesse Glick 2012-01-09 17:10:45 UTC does not list any OSGi bundles. Among other things, this means that an Ant-based NBM suite which uses autoupdate.catalog.url to download required clusters from the NB platform will be missing these bundles (e.g. com-jcraft-jsch.jar). does contain them, so there is nothing inherently wrong with the Ant tasks which generate update centers, just with how these were used for the release build.
Comment 1 Jesse Glick 2012-01-10 17:28:32 UTC
Complicates building of NB-Ruby against 7.1, and prevents SQE from doing so at all. Needs to be addressed soon.
Comment 2 pgebauer 2012-01-18 11:39:59 UTC
Could you please check whether the following AUC has fixed the problem?
Comment 3 Jesse Glick 2012-01-18 22:06:44 UTC
The AUC now includes the bundles. Unfortunately <autoupdate> still ignores the bundles since they have no targetcluster attribute, due to an apparent bug in <makeupdatedesc>; I am working on a fix, and you will need to regenerate the update center using a patched also fails to handle bundles at all, it turns out, which I will also fix, but that requires no attention from you as the UC creator. Anyone using bootstrap.url= will pick up that fix in due time.
Comment 4 Jesse Glick 2012-01-18 23:42:39 UTC
(In reply to comment #3)
> you will need to regenerate the
> update center using a patched
Comment 5 pgebauer 2012-01-23 13:51:12 UTC
I have refreshed the file

Could you please check it?
Comment 6 Jesse Glick 2012-01-23 22:41:42 UTC
Looks good so far as I can tell - please make it live.
Comment 8 Jesse Glick 2012-01-24 17:12:18 UTC
catalog.xml not only does not include OSGi bundles, but catalog_stage.xml now does not either.
Comment 9 Jesse Glick 2012-01-25 15:02:34 UTC
Seems to have been a DLC caching problem; fixed catalog.xml now live and confirmed in both SQE and community-ruby.
Comment 10 Quality Engineering 2012-01-25 16:36:05 UTC
Integrated into 'main-golden', will be available in build *201201250600* on (upload may still be in progress)
User: Jesse Glick <>
Log: #207075: more OSGi handling fixes.
Set targetcluster in updates.xml according to directory containing bundle.
If a bundle is downloaded, create config/Modules/*.xml for it and otherwise copy the JAR.
Comment 11 Jesse Glick 2012-03-03 00:17:58 UTC
*** Bug 209119 has been marked as a duplicate of this bug. ***
Comment 12 Jesse Glick 2012-03-03 00:18:25 UTC
Duplicate issue indicates that an UC on is still broken.
Comment 13 pgebauer 2012-06-12 13:02:40 UTC
I can see the correct catalog.xml at
Comment 14 Jesse Glick 2012-06-12 16:47:21 UTC still appears broken as mentioned in bug #209119.
Comment 15 pgebauer 2012-06-13 12:09:04 UTC
I have updated both catalog.xml and catalog.xml.gz at . 

However I would like to remark that the only valid and up to date catalogs reside at .
Comment 16 Jesse Glick 2012-06-13 17:25:47 UTC
(In reply to comment #15)
> the only valid and up to date catalogs reside at

Fine enough, since that is what harness/README suggests (via the redirect from But since at least someone has come across the UCs (as in bug #209119), these need to be either kept up to date as well, or deleted so that there is no chance of confusion.
Comment 17 Jackie_Rosen 2014-02-16 11:23:26 UTC
SPAM - Removed by Administrator