Problems installing Grails-Support extension

[zidjian]

Hello,

I'm trying for hours to install the STS with the Grails extension and always get the same error.
Anyhow the IDE cannot find the classes related to the grails plugin and I cannot figure out why.
I have a fresh install from STS and after installing the grails extension and rebooting I get following error:


The org.eclipse.jdt.ui.javaElementFilters plug-in extension "com.springsource.ide.grails.ui.hideSourceFoldersF ilters" specifies a viewer filter class which does not exist.
Plug-in com.springsource.sts.grails.ui was unable to load class com.springsource.sts.grails.ui.internal.filter.Pac kageExplorerFilter.
An error occurred while automatically activating bundle com.springsource.sts.grails.ui (906).


Hope anyone can help me out.
Thanks
Uli

[Andrew Eisenberg]

How are you installing the grails tooling? Through the extensions page? The nightly build?

I am going to install the nightly build right now and see if I can reproduce the problem.

[Andrew Eisenberg]

I have tried to reproduce this locally, but cannot. I am guessing that there must be something on your side.

This line: "An error occurred while automatically activating bundle com.springsource.sts.grails.ui (906)." indicates that there was a previous error that prevented the grails.ui plugin from being started. Do you have any other exceptions in your error log?

Are you perhaps behind a firewall? Is your STS directory read-only? Both of these have been known to cause problems in the past.

[ricgoto]

Was this issue resolved? What was the solution. I'm currently trying to install STS. I've tried the standalone SpringSource STS and I've also tried using Eclipse and the "Install New Software..." method. Both resulted in errors when restarting STS/Eclipse after the grails update:

The org.eclipse.jdt.ui.javaElementFilters plug-in extension "com.springsource.ide.grails.ui.hideSourceFoldersF ilters" specifies a viewer filter class which does not exist.
Plug-in com.springsource.sts.grails.ui was unable to load class com.springsource.sts.grails.ui.internal.filter.Pac kageExplorerFilter.
An error occurred while automatically activating bundle com.springsource.sts.grails.ui (341).

I've tried setting the entire springsource and eclipse directories as not read-only prior to and after updating. I've also disabled my firewall. Neither have worked.

Also, I was able to successfully install the STS with Grails on my laptop, but its just too slow to get any real work done on it.

[Andrew Eisenberg]

I have not heard back from the original poster of this question, so I am not sure if it has been successfully resolved.

However, I can try to see if we can get to the bottom of this through your installation.

Can you try the following:

1. What is the full stack trace of the related exception? It may be available in the error log view.
2. Can you look thrugh your error log for any other possibly related entries?
3. Go to Help -> About STS and click on Installation details. Please attach the contents of the congifuration page.

[ricgoto]

There seem to be several errors in the error view and log. I've attached it along with the configuration from the installation details in a ZIP file.

Thanks!

[Andrew Eisenberg]

Thanks for the information. Looking at your logs, it seems like your user.home system property is not set (or it's not valid).

Can you try editing the STS.ini file and adding the line:

-Duser.home=/path/to/your/user/home

On windows/linux the STS.ini is located in the sts-2.6.0-release folder.

On Mac, it is inside of the STS.app/Contents/MacOS folder.

This is something that we should fix inside of STS, or at least provide a nice error message. But please let me know if this addresses your problem.

[wlagrone]

Andrew:

I was struggling with the same problem this weekend and found that adding the -Duser.home directive as described resolved the problem for me.

In my situation I have STS installed on my C drive while My Documents is loaded on my D drive. The result is a problem similar to what is described in this thread.

anyway thanks for the help.

[Andrew Eisenberg]

Yep. That looks like the same problem. Thanks for linking this thread to the other. We'll work on something that will provide more descriptive error messages in case this happens to other users.

[ricgoto]

Andrew,

It worked. Thanks a lot!

Ricardo