myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <>
Subject [jira] Commented: (EXTSCRIPT-114) ExtScript fails to start when Groovy is not available
Date Sun, 18 Apr 2010 14:38:25 GMT


Werner Punz commented on EXTSCRIPT-114:

I have known this issue but forgot to add it to the jira, I will fix it next week during the
final testing round, thanks for reporting it,
this has to be fixed, I agree.

> ExtScript fails to start when Groovy is not available
> -----------------------------------------------------
>                 Key: EXTSCRIPT-114
>                 URL:
>             Project: MyFaces Extensions Scripting
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0-Beta-2
>         Environment: Vista x64, Java 6, jetty-6.1.14
>            Reporter: Jan-Kees van Andel
>            Assignee: Werner Punz
> When I don't add the groovy binaries to my Maven dependencies, and I run my app with
maven-jetty-plugin, I get the following exception:
> 2010-04-18 14:46:55.710::WARN:  Error starting handlers
> java.lang.NoClassDefFoundError: groovy/lang/GroovyObject
> 	at java.lang.ClassLoader.defineClass1(Native Method)
> 	at java.lang.ClassLoader.defineClass(
> 	at
> 	...
> I don't want to use Groovy, but I do need the Groovy binaries for ExtScript to start.
> Maybe this Exception should be used to automatically disable Groovy support?
> Anyway, I personally don't mind to add Groovy, but I think it should be fixed before
the 1.0 release b/c I think other users do mind.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message