facebook

plug-in "org.eclipse.wst.common.uriresolver" Maven

  1. MyEclipse IDE
  2.  > 
  3. Feature Requests
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #260072 Reply

    korayuygun
    Member

    Hi,
    I wanted to install Maven2, MyEclipse gives me this error message :
    MyEclipse Web Services Support (5.0.1) requires plug-in “org.eclipse.wst.common.uriresolver”

    Do you have any idea please?

    Thank you,
    Koray.

    #260174 Reply

    Riyad Kalla
    Member

    Koray,
    You mean when you run the Update Manager you are getting this problem?

    Can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.

    #260582 Reply

    Mark Scarton
    Member

    I am having the same problem. I’ve just installed the latest releases of Eclipse and MyEclipse and when I run the Update Manager | Find/Install | “Search for updates of the currently installed features”, I am receiving the error message “MyEclipse Web Services Support (5.0.1) requires plug-in “org.eclipse.wst.common.uriresolver”.

    *** Date: Tue Oct 17 12:32:51 CDT 2006

    *** Platform Details:

    REMOVED, please follow the posting guidelines for future posts.

    #260587 Reply

    Riyad Kalla
    Member

    mscarton, we believe this is a conflict with the new update set from the Eclipse/WTP groups. This will be resolved in the 5.0.3 release on Nov 6th, sorry for the trouble.

    #260634 Reply

    Mark Scarton
    Member

    How do I run the Update Manager in the mean time? I have a few plug-in’s that I have to have for product development. Right now, I receive the error message indicated and can go no further.

    #260636 Reply

    Riyad Kalla
    Member

    mscarton,
    This is currently a major design limitation of the update manager that has been discussed quite a bit in the Eclipse bug tracker. If the update manager hits any snag, with any plugin in the entire install, it will simply not run, regardless of the conflict.

    The only workaround I can think of at this time is to download the newer versions of those plugins and install them manually (e.g. unzipping them to your eclipse\plugins dir).

    #260643 Reply

    Mark Scarton
    Member

    Where can I obtain this plug-in? I’ve looked all over (for several hours) but could only find source. I don’t want to build it, just install it.

    btw: It surprises me that MyEclipse would put a broken release out without providing me with at least some form of a circumvention up front. I didn’t expect to have to spend several days getting the blasted thing to work.

    #260644 Reply

    Riyad Kalla
    Member

    mscarton,
    I understand you are frustrated but this is a problem you *will* encounter on the Eclipse platform anytime you mix together a sufficiently large number of plugins that all share the same dependencies. You will eventually hit a wall where one plugin (e.g. Visual Editor) will want to upgrade it’s dependency on GEF, where as another plugin (e.g. UML Tool) will not want it upgraded because it relies on the old version. In this case you will get a collision which is what you are experiencing now.

    The only solution is to wait for the lagging plugin to upgrade it’s dependencies. In this case MyEclipse is the lagging plugin (more specifically a collection about about 180 plugins, which is why it’s much easier to realize collisions with such a large product than a single plugin product like Subversion or the like).

    We are addressing this in our 5.0.3 release by upgrading all our dependencies to the latest stable versions of the libraries that we require which will remove this collision.

    As I said I’m sorry I cannot provide you a sufficient workaround for the other plugins you want to update at the moment, this is the result of this “all or nothing” behavior that the update manager takes on, leaving us or anyone else shipping a product that could cause a collision from time to time to be caught without many different options for helping our users around the issue.

    #261690 Reply

    eusholli
    Member

    Is this now fixed? I am getting the same error and downloaded the latest s/w over the weekend

    #261692 Reply

    Riyad Kalla
    Member

    Yes, all our dependencies were upgraded to the latest stable releases in the 5.1 release which is now based ontop of Eclipse 3.2.1.

Viewing 10 posts - 1 through 10 (of 10 total)
Reply To: plug-in "org.eclipse.wst.common.uriresolver" Maven

You must be logged in to post in the forum log in