http://updates.netbeans.org/netbeans/updates/7.1/uc/final/distribution/catalog.xml.gz 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).
http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz 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.
Complicates building of NB-Ruby against 7.1, and prevents SQE from doing so at all. Needs to be addressed soon.
Could you please check whether the following AUC has fixed the problem?
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 MakeUpdateDesc.java.
AutoUpdate.java 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=http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/netbeans/harness/tasks.jar will pick up that fix in due time.
(In reply to comment #3)
> you will need to regenerate the
> update center using a patched MakeUpdateDesc.java.
I have refreshed the file
Could you please check it?
Looks good so far as I can tell - please make it live.
I have updated 7.1 AUCs
catalog.xml not only does not include OSGi bundles, but catalog_stage.xml now does not either.
Seems to have been a DLC caching problem; fixed catalog.xml now live and confirmed in both SQE and community-ruby.
Integrated into 'main-golden', will be available in build *201201250600* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jesse Glick <email@example.com>
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.
*** Bug 209119 has been marked as a duplicate of this bug. ***
Duplicate issue indicates that an UC on bits.netbeans.org is still broken.
I can see the correct catalog.xml at http://dlc.sun.com.edgesuite.net/netbeans/updates/7.1/uc/final/distribution
http://bits.netbeans.org/netbeans/7.1/fcs/uc/catalog.xml.gz still appears broken as mentioned in bug #209119.
I have updated both catalog.xml and catalog.xml.gz at http://bits.netbeans.org/netbeans/7.1/fcs/uc/ .
However I would like to remark that the only valid and up to date catalogs reside at http://dlc.sun.com.edgesuite.net/netbeans/updates/7.1/uc/final/distribution/ .
(In reply to comment #15)
> the only valid and up to date catalogs reside at dlc.sun.com.edgesuite.net
Fine enough, since that is what harness/README suggests (via the redirect from updates.netbeans.org). But since at least someone has come across the bits.netbeans.org 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.
SPAM - Removed by Administrator