ExceptionInitializerError

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

ExceptionInitializerError

David Witherspoon
Hi there,

Out of the blue today, we are unable to build one of our components.  Here's a bit of the maven output plus the stack trace.

Downloaded: http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-01/groovy-eclipse-batch-2.0.7-01.pom (2 KB at 12.4 KB/sec)
Downloaded: http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-02/groovy-eclipse-batch-2.0.7-02.pom (2 KB at 18.3 KB/sec)
Downloaded: http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-01/groovy-eclipse-batch-2.1.5-01.pom (2 KB at 18.5 KB/sec)
Downloaded: http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.pom (2 KB at 13.3 KB/sec)
Downloaded: http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.jar (13923 KB at 25040.7 KB/sec)
[INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
java.lang.ExceptionInInitializerError
    at org.codehaus.jdt.groovy.integration.internal.MultiplexingParser.dietParse(MultiplexingParser.java:43)
    at org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:775)
    at org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:395)
    at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:485)
    at org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4130)
    at org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689)
    at org.codehaus.groovy.eclipse.compiler.GroovyEclipseCompiler.compile(GroovyEclipseCompiler.java:243)
    at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
    at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.NullPointerException
    at org.eclipse.jdt.groovy.core.util.ContentTypeUtils.<clinit>(ContentTypeUtils.java:45)
    ... 30 more


I don't get why 3 different versions of groovy-eclipse-batch are referenced...I can't find a pom.xml in any of our stuff doing that.

Searching around online didn't help much, but I did find one single reference (from today) of somebody having the same problem: http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=5035&p=122723&hilit=dietparse#p122723

 I definitely don't get what's going on!  Can anyone shed any light on this?

- David Witherspoon, Atlanta, GA
~~~~~~~~~~~~~~~~
"The problem with internet quotes is that you cannot verify their authenticity."  - Abraham Lincoln
Reply | Threaded
Open this post in threaded view
|

Re: ExceptionInitializerError

Andrew Eisenberg
Fixed now.

I published a new release of groovy-eclipse-batch yesterday that did
not work properly on groovy-eclipse-compiler 2.7.0-01.  I now
recommend using an explicit version of groovy-eclipse-batch in your
pom.  This will become mandatory for the 2.8.0 release of
groovy-eclipse-compiler.

On Tue, Jun 25, 2013 at 11:02 AM, David Witherspoon
<[hidden email]> wrote:

> Hi there,
>
> Out of the blue today, we are unable to build one of our components.  Here's
> a bit of the maven output plus the stack trace.
>
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-01/groovy-eclipse-batch-2.0.7-01.pom
> (2 KB at 12.4 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-02/groovy-eclipse-batch-2.0.7-02.pom
> (2 KB at 18.3 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-01/groovy-eclipse-batch-2.1.5-01.pom
> (2 KB at 18.5 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.pom
> (2 KB at 13.3 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.jar
> (13923 KB at 25040.7 KB/sec)
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> java.lang.ExceptionInInitializerError
>     at
> org.codehaus.jdt.groovy.integration.internal.MultiplexingParser.dietParse(MultiplexingParser.java:43)
>     at
> org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:775)
>     at
> org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:395)
>     at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:485)
>     at
> org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4130)
>     at org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689)
>     at
> org.codehaus.groovy.eclipse.compiler.GroovyEclipseCompiler.compile(GroovyEclipseCompiler.java:243)
>     at
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
>     at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
>     at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>     at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>     at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>     at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>     at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>     at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:597)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: java.lang.NullPointerException
>     at
> org.eclipse.jdt.groovy.core.util.ContentTypeUtils.<clinit>(ContentTypeUtils.java:45)
>     ... 30 more
>
> I don't get why 3 different versions of groovy-eclipse-batch are
> referenced...I can't find a pom.xml in any of our stuff doing that.
>
> Searching around online didn't help much, but I did find one single
> reference (from today) of somebody having the same problem:
> http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=5035&p=122723&hilit=dietparse#p122723
>
>  I definitely don't get what's going on!  Can anyone shed any light on this?
>
> - David Witherspoon, Atlanta, GA
> ~~~~~~~~~~~~~~~~
> "The problem with internet quotes is that you cannot verify their
> authenticity."  - Abraham Lincoln

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

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: ExceptionInitializerError

David Witherspoon
Ah, I see.

What version of groovy-eclipse-batch IS compatible with groovy-eclipse-compiler 2.7.0-01?



From: Andrew Eisenberg <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Tuesday, June 25, 2013 2:30 PM
Subject: Re: [groovy-eclipse-plugin-user] ExceptionInitializerError

Fixed now.

I published a new release of groovy-eclipse-batch yesterday that did
not work properly on groovy-eclipse-compiler 2.7.0-01.  I now
recommend using an explicit version of groovy-eclipse-batch in your
pom.  This will become mandatory for the 2.8.0 release of
groovy-eclipse-compiler.

On Tue, Jun 25, 2013 at 11:02 AM, David Witherspoon
<[hidden email]> wrote:

> Hi there,
>
> Out of the blue today, we are unable to build one of our components.  Here's
> a bit of the maven output plus the stack trace.
>
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-01/groovy-eclipse-batch-2.0.7-01.pom
> (2 KB at 12.4 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-02/groovy-eclipse-batch-2.0.7-02.pom
> (2 KB at 18.3 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-01/groovy-eclipse-batch-2.1.5-01.pom
> (2 KB at 18.5 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.pom
> (2 KB at 13.3 KB/sec)
> Downloaded:
> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.jar
> (13923 KB at 25040.7 KB/sec)
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> java.lang.ExceptionInInitializerError
>    at
> org.codehaus.jdt.groovy.integration.internal.MultiplexingParser.dietParse(MultiplexingParser.java:43)
>    at
> org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:775)
>    at
> org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:395)
>    at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:485)
>    at
> org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4130)
>    at org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689)
>    at
> org.codehaus.groovy.eclipse.compiler.GroovyEclipseCompiler.compile(GroovyEclipseCompiler.java:243)
>    at
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
>    at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
>    at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>    at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>    at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>    at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>    at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>    at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>    at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>    at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>    at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>    at java.lang.reflect.Method.invoke(Method.java:597)
>    at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>    at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>    at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>    at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: java.lang.NullPointerException
>    at
> org.eclipse.jdt.groovy.core.util.ContentTypeUtils.<clinit>(ContentTypeUtils.java:45)
>    ... 30 more
>
> I don't get why 3 different versions of groovy-eclipse-batch are
> referenced...I can't find a pom.xml in any of our stuff doing that.
>
> Searching around online didn't help much, but I did find one single
> reference (from today) of somebody having the same problem:
> http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=5035&p=122723&hilit=dietparse#p122723
>
>  I definitely don't get what's going on!  Can anyone shed any light on this?
>
> - David Witherspoon, Atlanta, GA
> ~~~~~~~~~~~~~~~~
> "The problem with internet quotes is that you cannot verify their
> authenticity."  - Abraham Lincoln

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

    http://xircles.codehaus.org/manage_email




Reply | Threaded
Open this post in threaded view
|

Re: ExceptionInitializerError

Andrew Eisenberg
2.1.3-01 and the recently released 2.1.5-03.  Also, 2.0.6-01 and
2.0.7-03 (the -01 and -02 versions are bad).



On Tue, Jun 25, 2013 at 11:49 AM, David Witherspoon
<[hidden email]> wrote:

> Ah, I see.
>
> What version of groovy-eclipse-batch IS compatible with
> groovy-eclipse-compiler 2.7.0-01?
>
>
> ________________________________
> From: Andrew Eisenberg <[hidden email]>
> To: "[hidden email]"
> <[hidden email]>
> Sent: Tuesday, June 25, 2013 2:30 PM
> Subject: Re: [groovy-eclipse-plugin-user] ExceptionInitializerError
>
> Fixed now.
>
> I published a new release of groovy-eclipse-batch yesterday that did
> not work properly on groovy-eclipse-compiler 2.7.0-01.  I now
> recommend using an explicit version of groovy-eclipse-batch in your
> pom.  This will become mandatory for the 2.8.0 release of
> groovy-eclipse-compiler.
>
> On Tue, Jun 25, 2013 at 11:02 AM, David Witherspoon
> <[hidden email]> wrote:
>> Hi there,
>>
>> Out of the blue today, we are unable to build one of our components.
>> Here's
>> a bit of the maven output plus the stack trace.
>>
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-01/groovy-eclipse-batch-2.0.7-01.pom
>> (2 KB at 12.4 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-02/groovy-eclipse-batch-2.0.7-02.pom
>> (2 KB at 18.3 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-01/groovy-eclipse-batch-2.1.5-01.pom
>> (2 KB at 18.5 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.pom
>> (2 KB at 13.3 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.jar
>> (13923 KB at 25040.7 KB/sec)
>> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
>> java.lang.ExceptionInInitializerError
>>    at
>>
>> org.codehaus.jdt.groovy.integration.internal.MultiplexingParser.dietParse(MultiplexingParser.java:43)
>>    at
>>
>> org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:775)
>>    at
>>
>> org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:395)
>>    at
>> org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:485)
>>    at
>>
>> org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4130)
>>    at org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689)
>>    at
>>
>> org.codehaus.groovy.eclipse.compiler.GroovyEclipseCompiler.compile(GroovyEclipseCompiler.java:243)
>>    at
>>
>> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
>>    at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
>>    at
>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>    at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>    at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>    at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>    at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>    at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>    at java.lang.reflect.Method.invoke(Method.java:597)
>>    at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>    at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>    at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>    at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>> Caused by: java.lang.NullPointerException
>>    at
>>
>> org.eclipse.jdt.groovy.core.util.ContentTypeUtils.<clinit>(ContentTypeUtils.java:45)
>>    ... 30 more
>>
>> I don't get why 3 different versions of groovy-eclipse-batch are
>> referenced...I can't find a pom.xml in any of our stuff doing that.
>>
>> Searching around online didn't help much, but I did find one single
>> reference (from today) of somebody having the same problem:
>>
>> http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=5035&p=122723&hilit=dietparse#p122723
>>
>>  I definitely don't get what's going on!  Can anyone shed any light on
>> this?
>>
>> - David Witherspoon, Atlanta, GA
>> ~~~~~~~~~~~~~~~~
>> "The problem with internet quotes is that you cannot verify their
>> authenticity."  - Abraham Lincoln
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>

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

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: ExceptionInitializerError

David Witherspoon
Here's what I used in my parent pom to fix this issue, with Andrew's excellent help, for anybody else bumping into this issue:
   :
   :
   <build>
      <pluginManagement>
         <plugins>
            <plugin>
               <groupId>org.apache.maven.plugins</groupId>
               <artifactId>maven-compiler-plugin</artifactId>
               <version>3.0</version>
               <configuration>
                  <compilerId>groovy-eclipse-compiler</compilerId>
                  <extensions>true</extensions>
                  <verbose>true</verbose>
               </configuration>
               <dependencies>
                  <dependency>
                     <groupId>org.codehaus.groovy</groupId>
                     <artifactId>groovy-eclipse-compiler</artifactId>
                     <version>2.7.0-01</version>
                     <exclusions>
                        <exclusion>
                           <groupId>org.codehaus.groovy</groupId>
                           <artifactId>groovy-eclipse-batch</artifactId>
                        </exclusion>
                     </exclusions>
                  </dependency>
                  <dependency>
                     <groupId>org.codehaus.groovy</groupId>
                     <artifactId>groovy-eclipse-batch</artifactId>
                     <version>2.1.3-01</version>
                  </dependency>
               </dependencies>
            </plugin>           
         </plugins>
      </pluginManagement>
   </build>

- David Witherspoon



From: Andrew Eisenberg <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Tuesday, June 25, 2013 2:58 PM
Subject: Re: [groovy-eclipse-plugin-user] ExceptionInitializerError

2.1.3-01 and the recently released 2.1.5-03.  Also, 2.0.6-01 and
2.0.7-03 (the -01 and -02 versions are bad).



On Tue, Jun 25, 2013 at 11:49 AM, David Witherspoon
<[hidden email]> wrote:

> Ah, I see.
>
> What version of groovy-eclipse-batch IS compatible with
> groovy-eclipse-compiler 2.7.0-01?
>
>
> ________________________________
> From: Andrew Eisenberg <[hidden email]>
> To: "[hidden email]"
> <[hidden email]>
> Sent: Tuesday, June 25, 2013 2:30 PM
> Subject: Re: [groovy-eclipse-plugin-user] ExceptionInitializerError
>
> Fixed now.
>
> I published a new release of groovy-eclipse-batch yesterday that did
> not work properly on groovy-eclipse-compiler 2.7.0-01.  I now
> recommend using an explicit version of groovy-eclipse-batch in your
> pom.  This will become mandatory for the 2.8.0 release of
> groovy-eclipse-compiler.
>
> On Tue, Jun 25, 2013 at 11:02 AM, David Witherspoon
> <[hidden email]> wrote:
>> Hi there,
>>
>> Out of the blue today, we are unable to build one of our components.
>> Here's
>> a bit of the maven output plus the stack trace.
>>
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-01/groovy-eclipse-batch-2.0.7-01.pom
>> (2 KB at 12.4 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.0.7-02/groovy-eclipse-batch-2.0.7-02.pom
>> (2 KB at 18.3 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-01/groovy-eclipse-batch-2.1.5-01.pom
>> (2 KB at 18.5 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.pom
>> (2 KB at 13.3 KB/sec)
>> Downloaded:
>>
>> http://nexus.axiomainc.com:8080/nexus/content/groups/public/org/codehaus/groovy/groovy-eclipse-batch/2.1.5-02/groovy-eclipse-batch-2.1.5-02.jar
>> (13923 KB at 25040.7 KB/sec)
>> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
>> java.lang.ExceptionInInitializerError
>>    at
>>
>> org.codehaus.jdt.groovy.integration.internal.MultiplexingParser.dietParse(MultiplexingParser.java:43)
>>    at
>>
>> org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:775)
>>    at
>>
>> org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:395)
>>    at
>> org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:485)
>>    at
>>
>> org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4130)
>>    at org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689)
>>    at
>>
>> org.codehaus.groovy.eclipse.compiler.GroovyEclipseCompiler.compile(GroovyEclipseCompiler.java:243)
>>    at
>>
>> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
>>    at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
>>    at
>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>    at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>    at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>    at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>    at
>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>    at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>    at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>    at java.lang.reflect.Method.invoke(Method.java:597)
>>    at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>    at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>    at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>    at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>> Caused by: java.lang.NullPointerException
>>    at
>>
>> org.eclipse.jdt.groovy.core.util.ContentTypeUtils.<clinit>(ContentTypeUtils.java:45)
>>    ... 30 more
>>
>> I don't get why 3 different versions of groovy-eclipse-batch are
>> referenced...I can't find a pom.xml in any of our stuff doing that.
>>
>> Searching around online didn't help much, but I did find one single
>> reference (from today) of somebody having the same problem:
>>
>> http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=5035&p=122723&hilit=dietparse#p122723
>>
>>  I definitely don't get what's going on!  Can anyone shed any light on
>> this?
>>
>> - David Witherspoon, Atlanta, GA
>> ~~~~~~~~~~~~~~~~
>> "The problem with internet quotes is that you cannot verify their
>> authenticity."  - Abraham Lincoln
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
>

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

    http://xircles.codehaus.org/manage_email