[jira] [Commented] (GROOVY-8017) unable to start any script using a CLIBuilder with groovy-all

2016-12-14 Thread JIRA
[ https://issues.apache.org/jira/browse/GROOVY-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15747630#comment-15747630 ] MichaƂ Zegan commented on GROOVY-8017: -- everything understood. You can close this issue > unable to

[jira] [Commented] (GROOVY-8017) unable to start any script using a CLIBuilder with groovy-all

2016-12-13 Thread Paul King (JIRA)
[ https://issues.apache.org/jira/browse/GROOVY-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746883#comment-15746883 ] Paul King commented on GROOVY-8017: --- Have you tried adding the commons cli jar to your classpath?

[jira] [Commented] (GROOVY-8017) unable to start any script using a CLIBuilder with groovy-all

2016-12-08 Thread Paul King (JIRA)
[ https://issues.apache.org/jira/browse/GROOVY-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733514#comment-15733514 ] Paul King commented on GROOVY-8017: --- Just a word on the name too. groovy-all contains all Groovy's

[jira] [Commented] (GROOVY-8017) unable to start any script using a CLIBuilder with groovy-all

2016-12-04 Thread Paul King (JIRA)
[ https://issues.apache.org/jira/browse/GROOVY-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721466#comment-15721466 ] Paul King commented on GROOVY-8017: --- Yes, you need to have the commons CLI jar on your classpath too.