Buildship 2.0.1 is now available

We are pleased to announce the Buildship 2.0.1 release. This release contains several fixes for bugs reported by our community. You can check out the list of changes on here.

Installation

Buildship 2.0.1 is available from the Eclipse Marketplace or from the eclipse.org update sites.

Buildship bug tracking

After the 2.0.0 release, we migrated our issues to GitHub. Please add :+1: for issues that you care about to help us prioritize them. Also, if you install the ZenHub extension in your browser, you’ll see an overview what’s happening in the Buildship project.

When I try to upgrade from Buildship 1 to 2 it Eclipse 4.6, I get the errors below. So I uninstall Buildship 1 and remove its update site. Still I get the same errors trying to install Buildship 2. Then when Eclipse restarts, the Buildship 2 update URL has been replace with Buildship 1.

An error occurred while collecting items to be installed
session context was:(profile=_Users_thad_Applications_eclipse_java-neon_Eclipse.app_Contents_Eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.gradleware.tooling.client,0.18.0.v20170220163122
No repository found containing: osgi.bundle,com.gradleware.tooling.model,0.18.0.v20170220163122
No repository found containing: osgi.bundle,com.gradleware.tooling.utils,0.18.0.v20170220163122
No repository found containing: osgi.bundle,org.eclipse.buildship.branding,2.0.1.v20170302-1039
No repository found containing: osgi.bundle,org.eclipse.buildship.core,2.0.1.v20170302-1039
No repository found containing: org.eclipse.update.feature,org.eclipse.buildship,2.0.1.v20170302-1039
No repository found containing: osgi.bundle,org.eclipse.buildship.stsmigration,2.0.1.v20170302-1039
No repository found containing: osgi.bundle,org.eclipse.buildship.ui,2.0.1.v20170302-1039
No repository found containing: osgi.bundle,org.gradle.toolingapi,3.4.0.v20170220163122

Unfortunately, I can’t reproduce the issue, the installation works fine for me locally. Nonetheless, I’ve created an issue for it on GitHub.

Odd. I’m seeing this on all three of my Eclipse Neon 4.6 installs, two on Mac Mini’s with Yosemite, and on a MacBook with El Capitan.

I’ve done a bunch of tests on Mac and on Linux. Everything seems fine. Can you please try installing/updating Buildship from the Eclipse Marketplace. Also, can you try cleaning up the ~/.eclipse and ~/.p2 folders?

That did it. Going through the Help -> Eclipse Marketplace… menu option showed a button “Installed.” Clicking on that it change to “Update Pending.” Click again, it changed to “Update,” and clicking on that finally updated it. (Ten years using Eclipse, and I’d always done it “by hand” till now.) Thanks.

1 Like