grails dsl-support and plugin_dsld_support build path problems

[mnebus]

Hello,

Sorry if this is something easy. I've search for a few hours and haven't found anything, but it's probably something obvious I'm missing.

This has been happening to me consistently when creating a new grails project in STS.

Every time I create a new grails project in STS, I end up with 2 Java Build Path Problems.

The container 'Grails Dependencies' references non existing library 'C:\athockey\tools\sts-2.9.1.RELEASE\plugins\com.springsource.sts.grails. resources_2.9.1.201203221000-RELEASE\dsl-support\'

The container 'Groovy DSL Support' references non existing library 'C:\athockey\tools\sts-2.9.1.RELEASE\plugins\org.codehaus.groovy_1.8.6.xx-20120301-1000-e37-RELEASE\plugin_dsld_support\'

(see attached image)
Capture.jpg


Java: 1.7.0_03 64-Bit
OS: Windows 7 Home Premium
STS/Grails-plugin: Version: 2.9.1.RELEASE - Build Id: 201203221000
Grails: 2.0.3
Groovy-Compiler: 1.8.6.xx-20120301-1000-e37-RELEASE
Groovy-eclipse-plugin: Version: 2.6.1.xx-20120301-1000-e37-RELEASE


What am I missing here?

Thanks,

-mike(n)

[Andrew Eisenberg]

Hi Mike,

It looks like the folders do not exist. Have a look at your filesystem and see if these folders exist:
'C:\athockey\tools\sts-2.9.1.RELEASE\plugins\com.springsource.sts.grails. resources_2.9.1.201203221000-RELEASE\dsl-support\'
'C:\athockey\tools\sts-2.9.1.RELEASE\plugins\org.codehaus.groovy_1.8.6.xx-20120301-1000-e37-RELEASE\plugin_dsld_support\'

There is a chance that you will see something like this instead:
'C:\athockey\tools\sts-2.9.1.RELEASE\plugins\com.springsource.sts.grails. resources_2.9.1.201203221000-RELEASE.jar'
'C:\athockey\tools\sts-2.9.1.RELEASE\plugins\org.codehaus.groovy_1.8.6.xx-20120301-1000-e37-RELEASE.jar'

If this is the case, then your installation is incorrect. These bundles should be exploded (ie- unzipped) in your plugins folder. If this is the case, then you will need to reinstall. Regardless, it looks like something is wrong with your installation, so that would probably be a good thing to do anyway.

[mnebus]

Thanks for the insight, I'll check it out when I get home tonight.
I do seem to remember that the directories did exist, but were empty. ...don't take that as gospel because it's been a few days now and I need to double check.

My installation process was as follows.
1. download/unzip sts (zip install, not exe)
2. open sts, select grails and groovy estensions
3. re-boot eclipse when installation is complete
4. create new grails project


You said, "there is a chance I'll see jar files" ...what case would that be?
I repeated this installation process multiple times in as much of a clean-room style as I could and still had the same result. Is it possible the zip installation of sts has something to do with it?

[Andrew Eisenberg]

You said, "there is a chance I'll see jar files" ...what case would that be?
I repeated this installation process multiple times in as much of a clean-room style as I could and still had the same result. Is it possible the zip installation of sts has something to do with it?

Sometimes people try to install by downloading a zip of the update site and copying the plugins and features into their Eclipse/STS installation. This won't work since the update site stores all of the plugins as jars, but they need to be exploded before they can be installed.

I don't know how these directories could be empty since all the install process does is downloads the jar and extracts the contents to your install location.

I have also seen situations where being behind a firewall causes some wackiness (but usually this corresponds to not being able to download at all).

I have also seen situations where installing into a read-only location causes problems. But again, the problem tends to manifest differently. ie- not being able to run the patched JDT compiler.

You could also try installing from the nightly update site:
http://dist.springsource.com/snapsho...S/nightly/e3.7
Add this to the work with section of Help -> Install new software... This may help, but only if the problem is with our update site (which is doubtful since no one else has reported this problem, but it may be worth a try).

[hanbo.wang]

Dear Andrew,

I got the same issue with Mike, and saw the following errors every time creating a new Grails project:

The container 'Grails Dependencies' references non existing library 'D:\SWAT\ggts-3.0.0-64bit\springsource\ggts-3.0.0.RELEASE\plugins\org.grails.ide.eclipse.resou rces_3.0.0.201208091000-RELEASE\dsl-support\'

The container 'Groovy DSL Support' references non existing library 'D:\SWAT\ggts-3.0.0-64bit\springsource\ggts-3.0.0.RELEASE\plugins\org.codehaus.groovy_1.8.6.xx-20120720-1100-e42\plugin_dsld_support\'

I can make sure the above 2 directories exist, please also see the screenshot.Attachment 5098

I'm using the latest GGTS zip package, and then install the m2e plugin, detail as below:

Groovy/Grails Tool Suite x86_64bit
Version: 3.0.0.RELEASE
Build Id: 201208091018

Win7 64bit
jvm C:/Program Files/Java/jdk1.6.0_25/bin/javaw.exe

thanks for your attention

regards,
Bob

[Andrew Eisenberg]

Can you be more specific? Exactly which folder is missing? Is it org.codehaus.groovy_1.8.6.xx-20120720-1100-e42 or plugin_dsld_support?

Do you have a org.codehaus.groovy_1.8.6.xx-20120720-1100-e42.jar file in the plugins folder? If yes, then this implies that groovy-eclipse is not installed properly and that you may have unzipped the update site instead of installed it through the update manager.