Spring Tool Suite 3.9 not working with Gradle Buildship 2.1.x

[ilya-kosolapov]

1. Use a nightly distribution build from http://dist.springsource.com/snapshot/STS/nightly-distributions.html (Tested with spring-tool-suite-3.9.1.CI-B204-e4.7.0-win32-x86_64.zip and spring-tool-suite-3.9.1.CI-B632-e4.6.3-win32-x86_64.zip)
2. Start STS, fresh workspace, Go to Eclipse Marketplace, search for and install Buildship Gradle Integration 2.0. Restart STS.
3. Try to import a gradle project by selecting File/Import.../Gradle/Existing Gradle Project, click Next.
4. Error is displayed: "Problem Opening Wizard. The selected wizard could not be started." The Details contains the following:

The selected wizard could not be started.
Plug-in "org.eclipse.buildship.ui" was unable to instantiate class "org.eclipse.buildship.ui.wizard.project.ProjectImportWizard".
loader constraint violation: loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) previously initiated loading for a different type with name "com/google/common/base/Optional"

Possibly related stack overflow question (submitted by a different person): https://stackoverflow.com/questions/45041310/spring-tool-suite-3-9-not-working-with-gradle-buildship

[martinlippert]

Buildship version 2.1.0 doesn't seem to work properly with STS 3.9.0, not sure yet what the underlying reason is.

The workaround for this is to uninstall the Buildship feature again via About -> Installation Details -> Installed Software, select the Buildship feature and press Uninstall.... Then go to the Install New Software and select the main Eclipse Oxygen repository from the dropdown. Type "buildship" in the filter box and install Buildship 2.0.x from there. This is also the officially released version of Buildship that comes with Eclipse Oxygen.

I will keep this open in order to figure out what is going wrong with Buildship 2.1.0 in STS, but I hope that the workaround helps in the meantime.

[martinlippert]

when using buildship 2.1.0 on STS 3.9.0, this appear in the Error Log View:

org.osgi.framework.BundleException: Could not resolve module: org.springframework.ide.eclipse.buildship20 [902]
  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.springframework.ide.eclipse.buildship20 [osgi.identity; type="osgi.bundle"; version:Version="3.9.0.201707061730-RELEASE"; osgi.identity="org.springframework.ide.eclipse.buildship20"; singleton:="true"] because it is exposed to package 'com.google.common.base' from resources com.google.guava [osgi.identity; type="osgi.bundle"; version:Version="21.0.0.v20170206-1425"; osgi.identity="com.google.guava"] and com.google.guava [osgi.identity; type="osgi.bundle"; version:Version="15.0.0.v201403281430"; osgi.identity="com.google.guava"] via two dependency chains.

Chain 1:
  org.springframework.ide.eclipse.buildship20 [osgi.identity; type="osgi.bundle"; version:Version="3.9.0.201707061730-RELEASE"; osgi.identity="org.springframework.ide.eclipse.buildship20"; singleton:="true"]
    require: (osgi.wiring.bundle=com.gradleware.tooling.model)
     |
    provide: osgi.wiring.bundle: com.gradleware.tooling.model
  com.google.guava [osgi.identity; type="osgi.bundle"; version:Version="21.0.0.v20170206-1425"; osgi.identity="com.google.guava"]

Chain 2:
  org.springframework.ide.eclipse.buildship20 [osgi.identity; type="osgi.bundle"; version:Version="3.9.0.201707061730-RELEASE"; osgi.identity="org.springframework.ide.eclipse.buildship20"; singleton:="true"]
    require: (osgi.wiring.bundle=org.springsource.ide.eclipse.commons.livexp)
     |
    provide: osgi.wiring.bundle; bundle-version:Version="3.9.0.201707061630-RELEASE"; osgi.wiring.bundle="org.springsource.ide.eclipse.commons.livexp"
  org.springsource.ide.eclipse.commons.livexp [osgi.identity; type="osgi.bundle"; version:Version="3.9.0.201707061630-RELEASE"; osgi.identity="org.springsource.ide.eclipse.commons.livexp"]
    require: (&(osgi.wiring.bundle=com.google.guava)(&(bundle-version>=15.0.0)(!(bundle-version>=16.0.0))))
     |
    provide: osgi.wiring.bundle: com.google.guava
  com.google.guava [osgi.identity; type="osgi.bundle"; version:Version="15.0.0.v201403281430"; osgi.identity="com.google.guava"]
	at org.eclipse.osgi.container.Module.start(Module.java:444)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

[martinlippert]

Looks like Buildship changed the dependency contraints on Guava from [15.0.0,16.0.0) to [15.0.0,22.0.0) (on the com.gradleware.tooling.model bundle).

This seems to cause a conflict, since we changed our dependency on guava to [15.0.0,16.0.0) to match the Buildship dependency and to explicitly avoid package-use constraint issues... :-(

This needs further testing and a more in-depth analysis why exactly the runtime is not able to find a wiring solution that satisfies both constraints. I guess just changing our dependency constraint again could cause STS to fail with older Buildship versions again... :-(

[spring-projects-issues]

(comment in Pivotal Tracker added by Martin Lippert:)

There is a new version of Buildship out there (2.1.1) that fixes this issue, therefore closing this ticket here.

[martinlippert]

In addition to the fix in Buildship 2.1.1 I also updated the dependency declarations in Spring IDE to avoid further conflicts in the future. I am using package-import all across the place now, hopefully this will help to avoid those issues in the future.