Failing to update Buildship from 1.0.15 to 1.0.20


(davidmichaelkarr) #1

I noticed yesterday that the update for Buildship to 1.0.20 was available. I had 1.0.15 installed at the time, in the latest Neon.

When I tried to update, I got the following:

An error occurred while collecting items to be installed
session context was:(profile=C__Users_dk068x_eclipse_java-neon_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.gradleware.tooling.client,0.16.0.v20160831165132
No repository found containing: osgi.bundle,com.gradleware.tooling.model,0.16.0.v20160831165132
No repository found containing: osgi.bundle,com.gradleware.tooling.utils,0.16.0.v20160831165132
No repository found containing: osgi.bundle,org.eclipse.buildship.branding,1.0.20.v20160901-0734
No repository found containing: osgi.bundle,org.eclipse.buildship.core,1.0.20.v20160901-0734
No repository found containing: osgi.bundle,org.eclipse.buildship.stsmigration,1.0.20.v20160901-0734
No repository found containing: osgi.bundle,org.eclipse.buildship.ui,1.0.20.v20160901-0734
No repository found containing: osgi.bundle,org.gradle.toolingapi,2.14.1.v20160831165132
No repository found containing: org.eclipse.update.feature,org.eclipse.buildship,1.0.20.v20160901-0734

What might be the problem here?


(Donát Csikós) #2

I’ve seen this kind of error when a misbehaving eclipse.org mirror was picked for the installation. Could you please try again?


(davidmichaelkarr) #3

I’ve tried it numerous times over the last 24 hours. Same result every time.


(Donát Csikós) #4

I was able to upgrade Buildship from 1.0.15 to 1.20 using Eclipse Neon using the http://download.eclipse.org/buildship/updates/e45/releases/1.0 update site. Is there something special about your environment? What Eclipse package do you use? What update sites you specify for the update?
As a fallback, can you try to uninstall Buildship and then install the latest version?


(davidmichaelkarr) #5

You’re using the “e45” update site to update Buildship on Neon? Isn’t “e45” for Mars? I’m using http://download.eclipse.org/buildship/updates/e46/releases/1.0 .

The other bizarre thing that is happening is that after I uninstall 1.0.15 and restart, verify from “Installation Details” that buildship is not installed, and then try to “install new software” using the above update site, it chugs for a while and then says:

Your original request has been modified.
“Buildship: Eclipse Plug-ins for Gradle” is already installed, so an update will be performed instead.

I then let it continue and it fails again with the above errors. I then cancel it out and look at “Installation Details”, and it does have 1.0.15 installed.

Very confusing.


(Donát Csikós) #6

The first Buildship version we compiled against Eclipse 4.6 was 1.0.17. You can see it if you unfold the content of the composite update site: http://download.eclipse.org/buildship/updates/e46/releases/1.0/?d
Besides, Buildship is uses a single codebase for all Eclipse versions, so an e45 build works well with e46.

Eclipse doesn’t handle uninstallation very well, because of caching/garbage collection in the provisioning platform. To get rid of the old version you can simply search-and-delete Buildship jars from Eclipse after uninstalling it.


(davidmichaelkarr) #7

This is really screwy. The neon.1 update came in, which upgraded Buildship to 1.0.18,but there’s still a pending update to 1.0.20. When I attempt it, I get the same errors as before.

I then tried uninstalling it first, but after shutting down Eclipse, I couldn’t find buildship jars anywhere. Not in the Eclipse distribution or in my workspace. I then started Eclipse again, and it showed version 1.0.18 installed. I then checked for updates again, and it offers the 1.0.20 version, which fails to install with the same errors as before.


(Lance Java) #8

I think it’s safer to revert to a previous install configuration and then install a new version of a plugin


(Donát Csikós) #9

That can be a good option, although my experience is that oftentimes it fails to revert to the previous state.


(Lance Java) #10

It’s always worked for me, perhaps it’s failing because you’ve manually deleted jars?


(Donát Csikós) #11

No, not because of that. Usually the revert fails because some update sites can’t be loaded. But we are not here to debug my environment :slight_smile:


(davidmichaelkarr) #12

Now that 1.0.21 is out, the update attempt gets the following:

An error occurred while collecting items to be installed
session context was:(profile=C__Users_dk068x_eclipse_java-neon_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.gradleware.tooling.client,0.16.0.v20160831165132
No repository found containing: osgi.bundle,com.gradleware.tooling.model,0.16.0.v20160831165132
No repository found containing: osgi.bundle,com.gradleware.tooling.utils,0.16.0.v20160831165132
No repository found containing: osgi.bundle,org.eclipse.buildship.branding,1.0.21.v20161010-1640
No repository found containing: osgi.bundle,org.eclipse.buildship.core,1.0.21.v20161010-1640
No repository found containing: osgi.bundle,org.eclipse.buildship.stsmigration,1.0.21.v20161010-1640
No repository found containing: osgi.bundle,org.eclipse.buildship.ui,1.0.21.v20161010-1640
No repository found containing: org.eclipse.update.feature,org.eclipse.buildship,1.0.21.v20161010-1640
No repository found containing: osgi.bundle,org.gradle.toolingapi,2.14.1.v20160831165132

(davidmichaelkarr) #13

I’ve managed to resolve this, but I think you should be examining that “e46” update site. I’ll explain why.

To be clear on one point, I’ve been saying that when I uninstall buildship and restart, by the time it finishes starting up again, when I check “Installation Details”, it shows Buildship is installed. It appears the “Startup Tasks” is somehow reinstalling it.

I was able to temporarily disable the startup tasks, so I was able to uninstall Buildship and restart, and it clearly showed when it was done starting up that Buildship isn’t installed.

However, it still fails with the same error as described earlier when I then try to install buildship 1.0.21.

So, I then changed my update site from the “e46” site to the “e45” site. This shouldn’t make any difference, as the same Buildship release is available at both update sites, and you say it should work fine with Neon.

And that worked. Buildship 1.0.21 installed fine when installed from the “e45” update site.

Clearly, something is subtly wrong with what’s available on the “e46” update site. Perhaps it only triggers with something in my environment, but that update site never worked for me, and the “e45” site did.


(Philip Arickx) #14

I had more or less the same issue : upgrading Neon (using Help -> Check For Updates) to Neon.1 gave me the “No repository found” errors for Buildship (gradleware tools and other related components).

I then upgraded by checking everything except Buildship, which gave me a working Neon.1 environment.

I kept running into the same issue trying to upgrade Buildship in various ways, but this method ended up working for me :

  • Go to MarketPlace and search for Buildship,
  • It comes up with status Installed. Still, click the “Install” button.
  • At this point, after a second or so, the Install button text changed to “Update”.
  • Click “Update”. It now installs Buildshuip successfully.

I verified, and the installation details gave me Buildship v 1.0.21


(nick heniser) #15

I had to do this for Oxygen, so must still be a problem sometimes. Thanks for the workaround.


(Christoph Büscher) #16

Same problem here with Oxygen, the workaround via the Marketplace install/update described by @PhRX worked for me as well. Thanks.