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: | Obsoleted modules on alpha dev daily AU | ||
|---|---|---|---|
| Product: | updatecenters | Reporter: | Jesse Glick <jglick> |
| Component: | AU Masters | Assignee: | rnovak <rnovak> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | issues, issues, pbuzek |
| Priority: | P3 | ||
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
Cleared cache. Removed files tomcat40.nbm, tomcat40-autocompile.nbm, tomcat40_ja.nbm, tomcat40_ru.nbm, jspie.nbm, jspie_ja.nbm, jspie_ru.nbm. The localized L10N NBMs may reappear as a part daily alpha NBMs build. http://www.netbeans.org/source/browse/www/www/updates/alpha/dev_1.6_.xml.diff?r1=1.160&r2=1.161 Does something need to be done manually when a module is removed from
nbbuild/build.properties:${config.modules.daily-alpha-nbms}, or is it
supposed to disappear from www/www/updates/alpha/dev_1.6_.xml
automatically during the next publishing cycle?
I won't pretend that I understand the meaning or purpose or policies surrounding the dev_1_6_.xml file, but here's the info requested by Jesse: JSP/Servlet (Advanced) (org.netbeans.modules.web.ie): this module was removed temporarily, will be readded when it compiles against the trunk again. HTTP Monitor: As Jesse says, this was added by me now and will continue to be a part of the build. Tomcat Server (org.netbeans.modules.web.tomcat.tomcat40) and Tomcat Server Autocompilation Support (org.netbeans.modules.web.tomcat.tomcat40.autocompile) These were removed as they are obsolete, replaced by Tomcat 5 Server (org.netbeans.modules.tomcat5) When the module is removed from daily-alpha-nbms configuration, it will stay on dev Alpha Update Centre, because the updating script is not able to recognize, whether the disappearance is caused by temporary compilation problems or by real removal from configuration. That's the reason for need of manual removal from local cache and rebuild of the catalog. Automated removal from Update Centre is more dangerous than keeping the NBM there. Even worse, when the updating script doesn't try to resolve/handle dependencies. Let me know your suggestions for better handling from independent script (build system independent update centre updater script). |
Running a current dev build against the alpha AU, I see ("new") modules in the Web category such as JSP/Servlet (Advanced) HTTP Monitor Tomcat Server Autocompilation Support Tomcat Server As for HTTP Monitor, I guess this will disappear from my list once I run a build that has monitor included (pjiricka just added it). But the three others were, I think, recently removed from the build by pbuzek, presumably because they are obsolete. It is therefore very misleading for them to appear on the dev alpha AU server as new add-on modules. They should probably be removed. Technically, www/www/updates/alpha/dev_1.6_.xml contains modules org.netbeans.modules.web.tomcat.tomcat40 org.netbeans.modules.web.tomcat.tomcat40.autocompile org.netbeans.modules.web.ie which I am guessing are now obsolete in dev builds (Pavel please confirm).