Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Run groovy scripts from sublime-text
{
"cmd": ["groovy", "$file"],
"selector": "source.groovy",
"file_regex": "[ ]*at .+[(](.+):([0-9]+)[)]",
"windows": {
"shell": "cmd.exe"
}
}
@kdabir

This comment has been minimized.

Copy link
Owner Author

commented May 7, 2012

If groovy is not found on PATH, check out here to set groovy on path for non terminal apps, or give complete path to groovy executable

@leonidasos

This comment has been minimized.

Copy link

commented Sep 21, 2012

Add selector for 'Automatic' build system:

"selector": "source.groovy",

@kdabir

This comment has been minimized.

Copy link
Owner Author

commented Aug 26, 2013

Thanks for the "selector" tip @leonidasos

@whgreate

This comment has been minimized.

Copy link

commented Sep 10, 2013

it works!

@jhntrifork

This comment has been minimized.

Copy link

commented Oct 10, 2013

If you add the line below, you will be able to use F4 to skip to next build error:
"file_regex": "[ ]*at .+((.+):([0-9]+))",

@seanf

This comment has been minimized.

Copy link

commented Feb 7, 2014

@jhntrifork, thanks for that. Sublime 3 gave an error about an escape character, so I went with this:

"file_regex": "[ ]*at .+[(](.+):([0-9]+)[)]",
@vherasme

This comment has been minimized.

Copy link

commented May 22, 2019

Hi. I am facing this issue on Ubuntu 18.04 with sublime text 3. Can anyone help?

This is my Groovy.sublime-build file:

{
    "cmd": ["groovy","$file_name"],
    "selector": "source.groovy",
    "file_regex": "[ ]*at .+[(](.+):([0-9]+)[)]",
    "shell": true
}

UPDATE:
I have solved by using the env option as incribed in this link. Now my *.build-system file looks like this:

{
    "cmd": ["/home/victor/.sdkman/candidates/groovy/2.5.7/bin/groovy $file_name"],
    "selector": "source.groovy",
    "file_regex": "[ ]*at .+[(](.+):([0-9]+)[)]",
    "shell": true,
    "env": {
    	"JAVA_HOME": "/home/victor/.sdkman/candidates/java/current"
    }
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.