After running updates from the update center the following modules have now broken.
Netbeans Plugin Development
When attempting to activate the following components the error is around versioning mismatch. Please see the attached
Unfortunately these features are now not available and two of them are extremely important (profiler and UML).
Created attachment 57762 [details]
Created attachment 57763 [details]
Created attachment 57764 [details]
reassign to autoupdate module for evaluation
atehrani, I think we need exact info in steps how to reproduce this error - what version of netbeans did you download,
which updates did you install etc, thanks.
ccing autoupdate and installer experts.
Patches are delivered by sustaining team, assign to Petr G.
Reporter, please attach you message to know more about your build and patches. Thanks
Btw. the latest NB6.0(.1) build worksforme, all updates can be applied without problems.
Product Version = NetBeans IDE 6.0.1 (Build 200801291616)
Operating System = Linux version 2.6.22-14-generic running on i386
Java; VM; Vendor = 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19; Sun Microsystems Inc.
Java Home = /usr/local/share/java/jdk1.6.0_04/jre
atehrani, didn't you add some other Update Center then defaults (6.1 Dev UC for example)? Thanks
This issue was also posted on nbusers list:
atehrani, you can use the Module Resolver module to resolve the problem:
Download it and install it in Tools|Plugins|Downloaded tab. Let me know if it helped to you and list of modules affected
able to reproduce on vista when running the IDE as normal user (issue doesn't appear when running netbeans as administrator)
i was able to reproduce too, when ide was installed + updated as root. Moduleresolver worked fine, it fixed missing
Lukasi + Tomasi!
That's cool you were able to reproduce this issue. Would you please add "steps to reproduce"? From reading this issue I
could not find it. I can only do "best guess", but that's not enough.
steps to reproduce:
1, install the IDE as root
2, start IDE as root
2, add all Updates that are available
3, close IDE
4, start IDE as normal user -> the disable modules message appears
this issue is caused by the appisuport/kit module in 601 patch1 that is installed to user directory athrought it should
be installed globally. The issue has been fixed in trunk already (jrechtacek, please confirm+provide issue #).
The resolver helps to the users to recover from the wrong IDE state. There is probably no other way how to help the
users that already get into this situation with 601patch1
I'm sorry to say that, but I was not able to reproduce it.
My configuration is Ubuntu Linux 7.10 (gutsy Gibon), using JavaSE 6U3 and 5U13, tried full installers of NetBeans 6.0
English and NetBeans 6.0.1 Multilanguage, always in default configurations (just accepted license and clicked Next all
the time till Finish). All tests were started with empty userdirs.
Would you please go into more details about you configuration (OS, username/privileges, JDK, which NB version and
edition was used)?
Would it be possible to check if you can reproduce the issue 2nd (3rd, 4th, etc) time?
Would it be possible to get our hands on your system?
Would it be possible to provide even more detailed steps to reproduce? For example the steps you provided miss
information about restart of IDE after update downloads or what exactly is meant under "Updates" - is it really just
updates from the "Updates" tab or also new plugins available from the "Available Plugins" tab?
> this issue is caused by the appisuport/kit module in 601 patch1 that is installed to user directory athrought it should
> be installed globally.
I vote for rollback of these changes we'd done in Patch 1 as a part of Patch 2. I don't understand why we didn't catch
this during testing of installation of Patch 1, this is serious and we need to avoid such mistakes in future.
Sustaining team, what type of tests you are running while testing installation of patches ?
Since the issue appearance is random and it looks like preponderance of NB Patch1 installations go well, changes will
not be rolled back so far. The issue will be kept open for recording of future issue appearances in order that steps to
reproduce will be determined.
the issue root cause was fixed by issue 128718
reassigning to auc where the issue can be tracked
unfortunatelly, we cannot do anything more with this issue.
I'm closing as duplicate of the issue that has been fixed in plugin manager. There is no solution for 6.0.1 users
because the plugin manager cannot update itself.
*** This issue has been marked as a duplicate of 128718 ***
Verified as duplicate of the other issue. No solution is available for 6.0/6.0.1 users.