Captain Man
Captain Man

Reputation: 7765

Spring Tool Suite says it could not create BootDashView (or any Spring view)

When I go to the "Boot Dashboard" (Update: actually I see similar messages on each Spring view) view I see the message

Could not create the view: org.springframework.ide.eclipse.boot.dash.views.BootDashView

There is an icon to see the error logs beside it, so I deleted them, reopened STS, and I did not see any error.

Any guidance on how to resolve this or further debug it?


More info

After following Martin's advice and opening the Host OSGi Console and typing ss to get the short status and doing diag <id> on a few different things all I was ever able to get was similar to this,

org.springframework.ide.eclipse.boot.dash [962]
  No resolution report for the bundle.

Martin mentioned looking for INSTALLED, but all I saw were ACTIVE, RESOLVED, STARTING, and <<LAZY>>. I ran diag on at least one bundle of each state, but got nothing any different than above (of course the names and IDs were different).

Upvotes: 3

Views: 11420

Answers (3)

Tom Bunting
Tom Bunting

Reputation: 1875

Just faced the same issue upgrading to latest STS 3.8.3 based on Neon.2 (4.6.2). Starting with the -clean option did nothing for me, neither did uninstalling / reinstalling the Groovy Eclipse feature as discussed.

What resolved it for me was switching to a new clean workspace - the boot dashboard then started working again. Oddly, it also works if I now switch back to the old workspace. Before this, the module was showing as LAZY in the Host OSGi console, now it's ACTIVE:

966 ACTIVE      org.springframework.ide.eclipse.boot.dash_3.8.3.201612191259-RELEASE

Upvotes: 1

Narasimha
Narasimha

Reputation: 1707

I was facing the similar issue with Spring Boot Dash view and using -clean option and restart STS worked for me.

Upvotes: 6

Captain Man
Captain Man

Reputation: 7765

The problem was one of my Groovy Eclipse compiler plugins (it was 1.8, 1.9, 2.0, 2.1, or 2.2, not sure which). After uninstalling it the Boot Dashboard no longer has an error.

Since part of my question was wondering about how to get better insight into the problem (more than checking the error log, which was empty) I will not mark this answer as accepted.

Upvotes: 0

Related Questions