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.

Bug 202388 - Update doesn't replace original module
Summary: Update doesn't replace original module
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Plugin Manager (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks: 202150
  Show dependency tree
 
Reported: 2011-09-21 07:58 UTC by Jiri Rechtacek
Modified: 2011-09-21 08:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Rechtacek 2011-09-21 07:58:40 UTC 
Install plugin A which depends on plugin B, then plugin B gets upgraded via the
standard update process, and then upgrade Netbeans, Netbeans won't start.  This
is because plugin A (which is still in the user folder) depends on plugin B
(which is now gone because it got moved to the previous shared folder).
Comment 1 Jiri Rechtacek 2011-09-21 08:06:13 UTC 
Works for me, PM installs update of module B (originaly installed in userdir) also install dir, regardless update of B declares own target cluster in IDE installation.
To run PM in verbose mode add a switch -J-Dorg.netbeans.modules.autoupdate.services.InstallManager.level=FINEST to etc/netbeans.conf Could you run your IDE with this switch and attach your messages.log for investigation what went wrong? Make sure you have not checked "Force install into shared directories" in PM Settings tab. Thanks