GPars 0.12 in Grails 1.3.7

[Pablo Molnar]

Hi there,

My integration tests bring the following exception using GPars data flows.

Caused by: java.lang.ClassNotFoundException: groovyx.gpars.actor.DefaultActor
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)


I'm aware about Grails 1.3.7 is bundled with GPars 0.9 and there is an issue trying to use the last version (http://stackoverflow.com/questions/7055571/grails-gpars-upgrade?answertab=votes#tab-top). Also I know that it was fixed in 2.0.0.M1 but unfortunately we are not able right now to perform such major upgrade.

Anyone knows if there is any workaround to exclude 0.9 via BuildConfig, compile events or something?

Kindly,
Pablo Molnar

[burtbeckwith]

No, unfortunately the classpath isn't configurable since it's set too early in the process. You need to either use 0.9 or upgrade to Grails 2.

Burt

> Hi there,
>
> My integration tests bring the following exception using GPars data flows.
>
> Caused by: java.lang.ClassNotFoundException:
> groovyx.gpars.actor.DefaultActor
>     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>
>
> I'm aware about Grails 1.3.7 is bundled with GPars 0.9 and there is an issue
> trying to use the last version (
> http://stackoverflow.com/questions/7055571/grails-gpars-upgrade?answertab=votes#tab-top).
> Also I know that it was fixed in 2.0.0.M1 but unfortunately we are not able
> right now to perform such major upgrade.
>
> Anyone knows if there is any workaround to exclude 0.9 via BuildConfig,
> compile events or something?
>
> Kindly,
> Pablo Molnar
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[sbglasius]

Hi,

How about renaming gpars-0.9.jar to gpars-0.9.backup and then rename gpars-0.12.jar to gpars-0.9.jar

I have not tried it with gpars, but had an error in groovy-all-1.7.8 and beanfields that went away when using groovy-all-1.7.10, so we renamed groovy-all-1.7.10 to 1.7.8 and the problem went away.

Major backdraw: You have to make the same manual process on all your grails installations (developer machines, CI servers etc...)

Med venlig hilsen / Best regards,
Søren Berg Glasius

Hedevej 1, Gl. Rye, DK-8680 Ry, Denmark
P: ([phone], M: ([phone], S: sbglasius
--- Press ESC once to quit - twice to save the changes.

2011/9/30 Burt Beckwith <[hidden email]>

No, unfortunately the classpath isn't configurable since it's set too early in the process. You need to either use 0.9 or upgrade to Grails 2.

Burt

> Hi there,
>
> My integration tests bring the following exception using GPars data flows.
>
> Caused by: java.lang.ClassNotFoundException:
> groovyx.gpars.actor.DefaultActor
>     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>
>
> I'm aware about Grails 1.3.7 is bundled with GPars 0.9 and there is an issue
> trying to use the last version (
> http://stackoverflow.com/questions/7055571/grails-gpars-upgrade?answertab=votes#tab-top).
> Also I know that it was fixed in 2.0.0.M1 but unfortunately we are not able
> right now to perform such major upgrade.
>
> Anyone knows if there is any workaround to exclude 0.9 via BuildConfig,
> compile events or something?
>
> Kindly,
> Pablo Molnar
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Pablo Molnar]

Apparently the issue is only present in grails test-app/run-app, however when I generate the war the dependencies are resolved fine. Sadly I'm not able to est my code...

Cheers,
Pablo

On Fri, Sep 30, 2011 at 6:34 AM, Søren Berg Glasius <[hidden email]> wrote:

Hi,

How about renaming gpars-0.9.jar to gpars-0.9.backup and then rename gpars-0.12.jar to gpars-0.9.jar

I have not tried it with gpars, but had an error in groovy-all-1.7.8 and beanfields that went away when using groovy-all-1.7.10, so we renamed groovy-all-1.7.10 to 1.7.8 and the problem went away.

Major backdraw: You have to make the same manual process on all your grails installations (developer machines, CI servers etc...)

Med venlig hilsen / Best regards,
Søren Berg Glasius

Hedevej 1, Gl. Rye, DK-8680 Ry, Denmark
P: <a href="tel:%28%2B45%2987880170" value="[phone]" target="_blank">([phone], M: <a href="tel:%28%2B45%2940449188" value="[phone]" target="_blank">([phone], S: sbglasius
--- Press ESC once to quit - twice to save the changes.

2011/9/30 Burt Beckwith <[hidden email]>

No, unfortunately the classpath isn't configurable since it's set too early in the process. You need to either use 0.9 or upgrade to Grails 2.

Burt

> Hi there,
>
> My integration tests bring the following exception using GPars data flows.
>
> Caused by: java.lang.ClassNotFoundException:
> groovyx.gpars.actor.DefaultActor
>     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>
>
> I'm aware about Grails 1.3.7 is bundled with GPars 0.9 and there is an issue
> trying to use the last version (
> http://stackoverflow.com/questions/7055571/grails-gpars-upgrade?answertab=votes#tab-top).
> Also I know that it was fixed in 2.0.0.M1 but unfortunately we are not able
> right now to perform such major upgrade.
>
> Anyone knows if there is any workaround to exclude 0.9 via BuildConfig,
> compile events or something?
>
> Kindly,
> Pablo Molnar
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email