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.
| Summary: | JNLP Shared Repository is missing AutoUpdate Services | ||
|---|---|---|---|
| Product: | www | Reporter: | Geertjan Wielenga <geertjan> |
| Component: | Builds & Repositories | Assignee: | nbbuild-issues@ide <nbbuild-issues> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | issues |
| Priority: | P2 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
Geertjan Wielenga
2007-08-14 10:21:20 UTC
1. RE problem; deadlock is building it: http://deadlock.netbeans.org/hudson/job/javadoc-nbms/lastSuccessfulBuild/artifact/nbbuild/build/jnlp/org-netbeans-modules-autoupdate-services.jnlp 2. You likely do not want to include the AU module in a JNLP app to begin with. It does not make any sense. So this means that when one distributes via web start, one shouldn't provide an update center. Makes sense, I suppose, because the modules you want to make available are made available via web start. But what if the user wants to install something from the Plugin Portal or elsewhere? You cannot mix AU and JNLP. The platform in JNLP mode does not use clusters in the usual way at all. You need to either provide all desired modules over JNLP (you could in principle offer a servlet-based .jnlp which lets users customize what they get), or offer a regular AU-based build. Makes sense to close this one, will be explained in tutorial, if at all. |