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: | Cannot install Scan On Demand module using 6.8 RC1 | ||
---|---|---|---|
Product: | contrib | Reporter: | dlipin <dlipin> |
Component: | Code | Assignee: | rnovak <rnovak> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | matusdekanek, michaelnazarov, mmirilovic, pflaska |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
dlipin
2009-11-27 05:10:11 UTC
Please reassign back to me and platform/Autoupdate after you make sure that dependencies are OK. Or fix the dependencies and publish the update on UC. Thanks. Connected to: http://hg.netbeans.org/jet-main/rev/36427ecf6f17 But fixed for contrib modules too: http://hg.netbeans.org/main/contrib/rev/893a5f4dfd92 Looks like new module has not been propagated to AU. Locally built NBM works without any problem in 6.8 rc1. We will discuss with Robert why old 1.11.2 module on AU was not updated to new 1.12.2. Robert will upload new version of module to AU. Pavel, I wish to extend AutoUpdate (and write an appropriate test) to catch such issues in future and show a warning before proceeding with the installation. Did I get it right, that the issue is that scanondemand module have the dependency "org.netbeans.modules.parsing.api = 2" (which means that release version is 0, impl version is 2), and the parsing api module is in fact "org.netbeans.modules.parsing.api/1" (release version is 1) and such situation is not caught as the error, right? PS. the important thing is that impl version if parsing api has not changed though release one has changed. Just for the record - I`ve filed Issue 177922 against AU. The new version of the module is now available on the UC. Dmitry, I have no idea how dependencies resolution works. I think there was only release version change. Dependencies were updated correctly, but the module was not uploaded, I do not know, how it works. Sorry. |