GRECLIPSE

Cannot find a solution satisfying the following requirements org.eclipse.mylyn.context_feature.feature.group [3.2.1.v20090722-0200-e3x].

Details

  • Type: Sub-task Sub-task
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.0.0alpha
  • Fix Version/s: 2.0.0m2
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Creating sub-task for this issue because it does seem to be a different problem than the one I fixed, even if it is the problem originally described.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Eisenberg added a comment -

Well, I just wrote a novel as to what I think is going on, and then the jira server crashed before I could submit and subsequently my firefox crashed as well. So, this was all lost.

To summarize from memory:

Older versions of groovy-eclipse did not allow some people to upgrade. I believe there were 2 reasons for this:

1. the version of jdt.core being shipped with the core patch
2. the version of commons.lang.

All versions after September 20 or so should allow you to upgrade to a new upgrade. On 3.4, however, there was a gap in snapshots from August 19 until September 22. I believe you are probably trying to upgrade from a mid-August snapshot to the September 22 one. Am I right?

Eclipse 3.4 does not generally provide understandable P2 error messages. However, I believe that you are hitting #2 above since the mylyn feature depends on commons.lang as well.

I recommend that you uninstall your current version of groovy-eclipse and then install the newer version. I have successfully installed the new version of groovy-eclipse in a fresh copy of STS 2.1.0 for E3.4, so hopefully you can too.

The real test will come when you try to upgrade from the September 22 version to a new version.

Please let me know if this works for you.

Show
Andrew Eisenberg added a comment - Well, I just wrote a novel as to what I think is going on, and then the jira server crashed before I could submit and subsequently my firefox crashed as well. So, this was all lost. To summarize from memory: Older versions of groovy-eclipse did not allow some people to upgrade. I believe there were 2 reasons for this: 1. the version of jdt.core being shipped with the core patch 2. the version of commons.lang. All versions after September 20 or so should allow you to upgrade to a new upgrade. On 3.4, however, there was a gap in snapshots from August 19 until September 22. I believe you are probably trying to upgrade from a mid-August snapshot to the September 22 one. Am I right? Eclipse 3.4 does not generally provide understandable P2 error messages. However, I believe that you are hitting #2 above since the mylyn feature depends on commons.lang as well. I recommend that you uninstall your current version of groovy-eclipse and then install the newer version. I have successfully installed the new version of groovy-eclipse in a fresh copy of STS 2.1.0 for E3.4, so hopefully you can too. The real test will come when you try to upgrade from the September 22 version to a new version. Please let me know if this works for you.
Hide
Permalink
Dave Syer added a comment -

Didn't work for me because I was installing from scratch (nothing to uninstall). And this is definitely post Sep 22.

What did work however (strange voodoo) was to install the JDT patch first on its own and then the Groovy feature with a restart in between the two. Go figure.

I wish someone in the world would take responsibility for P2 and its general crappiness (not pointing fingers here at all, just a general moan).

Show
Dave Syer added a comment - Didn't work for me because I was installing from scratch (nothing to uninstall). And this is definitely post Sep 22. What did work however (strange voodoo) was to install the JDT patch first on its own and then the Groovy feature with a restart in between the two. Go figure. I wish someone in the world would take responsibility for P2 and its general crappiness (not pointing fingers here at all, just a general moan).
Hide
Permalink
Andrew Eisenberg added a comment -

That is strange. The STS version that you are using, have you made any configuration changes to it?

The next time you try to update, please post here whether or not you have been successful.

Show
Andrew Eisenberg added a comment - That is strange. The STS version that you are using, have you made any configuration changes to it? The next time you try to update, please post here whether or not you have been successful.
Hide
Permalink
Andrew Eisenberg added a comment -

Is this still a problem for you?

Show
Andrew Eisenberg added a comment - Is this still a problem for you?
Hide
Permalink
Andrew Eisenberg added a comment -

OK. Closing this bug as I believe it is fixed due to recent changes in the update site structure. Please reopen or create a new bug if you continue to see problems.

Show
Andrew Eisenberg added a comment - OK. Closing this bug as I believe it is fixed due to recent changes in the update site structure. Please reopen or create a new bug if you continue to see problems.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.