How to get sources for Grails dependencies

I

2

7

How can I get Ivy to download the sources for dependencies from within Grails?

I tried editing all the ivy.xml files I could find as per this, but no luck.

~/.grails/1.3.4/projects/workspace-sts/integration-files/ivy.xml
/c/grails-1.3.4/src/grails/ant/ivy.xml

I've been reading the grails source, and can't find any way to do this. Does anyone have any ideas?

Inapplicable answered 31/8, 2010 at 13:35 Comment(0)

C

6

Grails Eclipse Scripts Plugin

Contredanse answered 31/8, 2010 at 19:55 Comment(3)

This doesn't work for me on Windows 7 / SpringSource Tool Suite 2.3.3.CI-R5572-B51 / Grails 1.3.4 without heavy modification. For example, the "eclipse_workspace_settings.epf" file it generates has "C:\adsf\asdf" paths, whereas eclipse seems to need "C\:/asdf/asdf" style paths for the file to be accepted. It did get me most of the way there though. – Inapplicable 3/9, 2010 at 15:18

Grails developers says that there would be more flexible dependency management starting from 1.3.5 or 1.4.0. But till that happened the only solution is to use Eclipse Scripts Plugin - fully or to create own plugin based on it. – Contredanse 3/9, 2010 at 19:41

That's because this kind of plugin is developped once and hardly maintained. Once the integration on the IDE side is more solid you don't need it at all. – Delisadelisle 16/3, 2012 at 13:17

F

11

I just use:

grails refresh-dependencies --include-source

Flickinger answered 29/8, 2014 at 17:22 Comment(0)

C

6

Grails Eclipse Scripts Plugin

Contredanse answered 31/8, 2010 at 19:55 Comment(3)

This doesn't work for me on Windows 7 / SpringSource Tool Suite 2.3.3.CI-R5572-B51 / Grails 1.3.4 without heavy modification. For example, the "eclipse_workspace_settings.epf" file it generates has "C:\adsf\asdf" paths, whereas eclipse seems to need "C\:/asdf/asdf" style paths for the file to be accepted. It did get me most of the way there though. – Inapplicable 3/9, 2010 at 15:18

Grails developers says that there would be more flexible dependency management starting from 1.3.5 or 1.4.0. But till that happened the only solution is to use Eclipse Scripts Plugin - fully or to create own plugin based on it. – Contredanse 3/9, 2010 at 19:41

That's because this kind of plugin is developped once and hardly maintained. Once the integration on the IDE side is more solid you don't need it at all. – Delisadelisle 16/3, 2012 at 13:17

Recommended topics

Hot tags