I've installed M8 and latest daily build. Everything works fine. Then I've
uninstalled latest daily - OK. The I've tried to uninstall M8 - Exception and
Second run worked fine so I decided to set priority not 1 but 2...
Created attachment 41531 [details]
No, second run failed as well, so P1.
Seems a duplicate of 102224.
*** This issue has been marked as a duplicate of 102224 ***
Exception looks similar but I did not touch GF in my uninstallations...
Let's wait and see whether the fix for 102224 will correct this one as well.
I'll include your use case in the fix verification procedure.
How is it going with verification? Build Apr 25 affected as well while other
issue marked as fixed...
Well as I can see this is not duplicate because issue still present.
Scenario looks very probable for end users who downloaded M8 and wants to update
1. Install M8.
2. Install M9.
3. Play around starting/stopping IDEs and ASes (possible this step is not required).
3. Open Add/Remove programs.
4. Click Remove on M9 then Cancel (possible this step is not required).
5. Click Remove on M8, Uninstall.
Exception same as screenshoted already.
I checked again: additional steps are not required. M8 installation became
uninstallable immediately after M9 installation.
Checked for Solaris 10 x86. Issue is reproducible.
But different exception throws - NoSuchMethodError. Screenshot attached.
Created attachment 41976 [details]
Seems to be fixed, please verify on M8 and next nighly build.
Added this item to the M9 release notes per Sergey's request.
Issue #102287: Cohabitation issues between Milestone 8 and Milestone 9 builds.
Description: You may encounter uninstallation problems if you have NetBeans 6.0
Milestone 9 and NetBeans 6.0 Milestone 8 installed simultaneously.
Workaround: Please follow the steps described in the Troubleshooting section of
the Installation Instructions.
Reproduced with M8+May 02M9.
As you could possible see the targeted milestone is M10.
So please verify not on the M9 installers but on the nightly build (from trunk).
Hmm, may be. I'll try then...
No need to release note the issue as it has been fixed.
Please be specific: has it been fixed in M9 or in M10? The Release Notes are for
M9 right now, so we need confirmation that this issue needs to be removed from
the currently posted release notes:
Annette, as you can probably see the targeted milestone is milestone 10.
So the issue is not fixed in M9 and is not required to be removed from already
posted release notes.
Verified on builds M8 and 200705250000 on Solaris x86 with JDK 1.5_11