[Dennis Simpson]

I get “conflicts” if I try to install Subversion

Eclipse 3.2
MyEclipse 5.0.1GA

I tried to install the latest Subclipse 1.0.3 (SubVersion plugin)

It listed conflicts with a large number of plugins, such as:
MyEclipse Web Services Support
MyEclipse JSP Design,
.. Struts
… Spring,
plus many more

The message said there were duplication conflicts and if you continue with the installation some parts may no longer work.

What does this mean?

Each conflict had two conflicts listed: one in eclipse and one in myeclipse.

[Riyad Kalla]

Unfortunately this is a limitation of the eclipse update manager and has an associated bug filed for it in bugzilla. The problem is that if there are *any* plugin conflicts in your workspace, the update manager cannot install anything. More specifically, if you installed Eclipse, then a ton of plugins like WTP, EMF, GEF, etc. and then MyEclipse. The conflict could be comming from the fact that MyEclipse ships all these plugins already, so you are getting a totally unrelated plugin conflict between your base Eclipse install and MyEclipse, so the update manager won’t install subclipse for you. The problem is not actualyl with subclipse, it works fine.

[jacob@well.com]

This is a pretty serious problem for me – I must have Subclipse installed as well, and it’s not just an informative error message, but in “Find and Install Updates…” I cannot install any updates at all. Both the “Next >” and “Finish” buttons in the “Updates” dialog are greyed out.

I am getting messages like MyEclipse Web Services Support (5.0.1) requires plug-in “org.eclipse.wst.common.uriresolver” – actually a whole string of similar messages.

I appreciate that you’ve filed a bug, but I didn’t have this problem using the previous version of Eclipse & MyEclipse.

This is with Eclipse 3.2.0 and MyEclipse 3.8.2 on SuSE Linux.

[Riyad Kalla]

Jacob & others,
The first step is to figure out which plugins are having problems with eachother. You can do this by creating a new workspace, and checking your new log file right after startup (<workspace dir>\.metadata\.log) and see if there are startup errors.

The fastest way is to check your <eclipse>\plugins directory to see if there are any duplicate or conflicting plugins there that are ALSO included in your <myeclipse installation dir>\eclipse\plugins dir (note that I’m referring to two different plugins dir, the eclipse one and myeclipse one)

EVen though this really shouldn’t be causing failures, I think that’s a place to start.

And the fastest way to fix the problem is to reinstall a clean Eclipse 3.2 SDK and MyEclipse 5.0.1 to new directories (never overwrite old directories) and then open your old workspace, viola. (although you will need to re-add any old 3rd party plugins you were using, which is sometimes a pain and othertimes not a problem at all)

[Author]

Posts