Eclipse 3.5.1 (Galileo SR1) is out!

Eclipse 3.5.1 (Galileo SR1) is out!

Eclipse 3.5.1 was just released! This is a service release as part of the Eclipse Galileo release train.

Inside Eclipse, you can use p2 to update with this URL:

If you’re only interested in Equinox, you can grab it here:

Finally the readme is here:

So what are you waiting for, update to get the latest bugfixes!

If you want to live on the bleeding edge, check out the latest Eclipse 3.6 (Helios) milestone.

8 Comments
  • Posted at 6:11 pm, September 25, 2009

    I think you meant

    http://download.eclipse.org/eclipse/updates/3.5/R-3.5.1-200909170800

    as p2 reporitory URL for Eclipse Platform?

  • Mark Phippard
    Posted at 6:54 pm, September 25, 2009

    If you are inside Eclipse shouldn’t you be able to just “Check Updates”?

  • Posted at 7:36 pm, September 25, 2009

    Of course, Mark, you are correct.

    If you are using Eclipse Classic, there are two predefined p2 repositories (Eclipse Platform plus Galileo). If you have downloaded one of the other EPP packages, there are at least three p2 repositories (EPP, Galileo, Eclipse) included that are used for updates.

  • Posted at 5:22 pm, September 28, 2009

    The update URL gives me a 404.

  • Posted at 5:25 pm, September 28, 2009
  • Steve Robenalt
    Posted at 11:15 pm, October 1, 2009

    This is probably an FAQ, but if so, I haven’t found it yet. After several days of failed attempts, I finally caught Denis’ blog post today explaining the problems with the 3.5.1 distribution. I started over again today via the p2-based update manager. Everything in the update appeared normal, so I chose to restart eclipse, rather than simply apply the changes. Unfortunately, Eclipse now refuses to start, giving me some 396 kb of log files to dig through, and reporting a failure to resolve some bundles. So far, each one I’ve spot checked is there, so it’s got to be deep in the dependency stack, or possibly a corrupt file or metadata somewhere, which leads me to my (probable) FAQ:

    Is there a way to validate the contents of my current installation to determine what the root cause is without dissecting the entire log? Failing that, doesn’t p2 allow me to roll back to an earlier valid installation?

    I haven’t filed a bug yet, because at the moment, I’m presuming this is self-inflicted.

    Thanks for any advice you can offer.