Would going back to 2.9.0 fix this issue?
I've also noticed that the Plugin search site is down, would that have anything to do with it?
http://grails.org/plugin/search
I'm getting a 503 and when it does come up sporadically it's really super slow.
Would going back to 2.9.0 fix this issue?
I've also noticed that the Plugin search site is down, would that have anything to do with it?
http://grails.org/plugin/search
I'm getting a 503 and when it does come up sporadically it's really super slow.
To fix your problem you only need to update the 'Grails Support' tools.
When you do that, the installer will figure out dependencies.
It looks like you can't upgrade because of this
'bundle org.eclipse.mylyn.tasks.ui [3.7.0,4.0.0)' but it could not be found.
Mylin is softwarethat comes from Eclipse (i.e. it isn't part of STS itself, but it normally comes bundled when you download
the full STS package, which contains Eclipse inside). Normally the installer should be able to find it in one of the update sites that are automatically configured with STS. But there has been recent version changes in mylin so that could be the reason for the problem.
Let me figure out what update site you could add to satisfy this dependency.
I'll get back to you shortly.
Kris
Kris De Volder -- SpringSource
I use the full zip version to install if that helps.
Any idea if going back to 2.9.0 would fix the issue?
Can you please try adding this site:
http://download.eclipse.org/mylyn/snapshots/3.7/
to your list of 'Available Software sites' (there is a link just below the box where you past an update site address, click that link and add this site.
Then try to update the Grails tooling again. Make sure that you have 'Contact all Update sites' box checked so that the installer will be able to find mylin version 3.7.
Let me know how that goes.
Kris
Kris De Volder -- SpringSource
> Any idea if going back to 2.9.0 would fix the issue?
If you mean the plugin manager problem. You could try but I don't think it will help. The bug has been there for a rather long time. It has just been latent. It is only triggered by certain contents of the plugin list file from grails.org. Apparantly the conditions that triggered this didn't happen much before. Since the trigger for the bug is in the contents of a downloaded file. It doesn't really help if you use 2.9.0 or 2.9.1. Only upgrading to a version that has the bugfix will really help avoid the problem.
Kris
Kris De Volder -- SpringSource
Adding the other site and performing the update worked.
Thank you!
Great! Thanks for letting me know.
Kris
Kris De Volder -- SpringSource
Kudos. Thanks for fixing this! It had been a source of annoyance for me for the last week or so, and I finally decided to try and figure out what was going on. A quick search led me here, and bam!, all better now.