[
https://issues.apache.org/jira/browse/GROOVY-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15721466#comment-15721466
]
Paul King commented on GROOVY-8017:
-----------------------------------
Yes, you need to have the commons CLI jar on your classpath too. Groovy does
bundle a jarjar'd version of commons cli for its own purposes but so as not to
impose that version on your scripts/classes, it requires you to use your own
version.
> unable to start any script using a CLIBuilder with groovy-all
> -------------------------------------------------------------
>
> Key: GROOVY-8017
> URL: https://issues.apache.org/jira/browse/GROOVY-8017
> Project: Groovy
> Issue Type: Bug
> Components: groovy-runtime
> Affects Versions: 2.4.7
> Reporter: Michał Zegan
> Priority: Critical
>
> It seems that groovy-all package does not work when trying to run a script
> that uses a command line parser like groovy.util.CLIBuilder.
> I have tried to run my script directly, adding groovy-all and ivy to
> classpath and using groovy.ui.GroovyMain as a main class. This is the error
> that I got:
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> General error during class generation: java.lang.NoClassDefFoundError: Unable
> to load class groovy.util.CliBuilder due to missing dependency
> org/apache/commons/cli/ParseException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
