You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Filippo Diotalevi <fi...@gmail.com> on 2006/12/02 13:11:43 UTC
error: compiler message file broken:
Hi, I've just came back after a couple of days out of town,
synchronized the trunk,
mvn clean install
and....
[INFO] [compiler:compile]
Compiling 572 source files to
/home/fdiotalevi/workspaces/openejb3/container/openejb-core/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
error: compiler message file broken: key=compiler.err.file
org/apache/geronimo/kernel/Kernel.class not found arguments={0}, {1},
{2}, {3}, {4}, {5}, {6}, {7}
.. am I missing anything?
--
Filippo
Re: error: compiler message file broken:
Posted by Filippo Diotalevi <fi...@gmail.com>.
> > Strange. Let me add that as a dep and see if it doesn't make the
> > problem go away.
>
> Looks like we already had a dep on that jar but it was excluded
> elsewhere... I removed that exclusion and a couple other ones too.
>
> This working for anyone not on a Mac?
Yes, it works now.. thanks!
--
Filippo
Re: error: compiler message file broken:
Posted by David Blevins <da...@visi.com>.
On Dec 2, 2006, at 3:06 PM, David Blevins wrote:
>
> On Dec 2, 2006, at 11:03 AM, Filippo Diotalevi wrote:
>
>> On 12/2/06, Manu George <ma...@gmail.com> wrote:
>>> Hi Jacek/Filippo,
>>> I am also getting this error now with a fresh
>>> checkout.
>>> Doing a google search gives some info that it is an error in the
>>> java
>>> compiler.
>>
>> Yes... it's a weird error.
>> I tried to checkout the previous version from svn (rev 481478) and I
>> managed to compile it successfully.
>>
>> Apparently, the stacktrace is telling me that the compiler cannot
>> find
>> the class org/apache/geronimo/kernel/Kernel.class.. the weird part is
>> that this class is never used in the code (it appears just in a
>> couple
>> of commented lines...)
>
> Strange. Let me add that as a dep and see if it doesn't make the
> problem go away.
Looks like we already had a dep on that jar but it was excluded
elsewhere... I removed that exclusion and a couple other ones too.
This working for anyone not on a Mac?
-David
Re: error: compiler message file broken:
Posted by David Blevins <da...@visi.com>.
On Dec 2, 2006, at 11:03 AM, Filippo Diotalevi wrote:
> On 12/2/06, Manu George <ma...@gmail.com> wrote:
>> Hi Jacek/Filippo,
>> I am also getting this error now with a fresh
>> checkout.
>> Doing a google search gives some info that it is an error in the java
>> compiler.
>
> Yes... it's a weird error.
> I tried to checkout the previous version from svn (rev 481478) and I
> managed to compile it successfully.
>
> Apparently, the stacktrace is telling me that the compiler cannot find
> the class org/apache/geronimo/kernel/Kernel.class.. the weird part is
> that this class is never used in the code (it appears just in a couple
> of commented lines...)
Strange. Let me add that as a dep and see if it doesn't make the
problem go away.
-David
Re: error: compiler message file broken:
Posted by Filippo Diotalevi <fi...@gmail.com>.
On 12/2/06, Manu George <ma...@gmail.com> wrote:
> Hi Jacek/Filippo,
> I am also getting this error now with a fresh checkout.
> Doing a google search gives some info that it is an error in the java
> compiler.
Yes... it's a weird error.
I tried to checkout the previous version from svn (rev 481478) and I
managed to compile it successfully.
Apparently, the stacktrace is telling me that the compiler cannot find
the class org/apache/geronimo/kernel/Kernel.class.. the weird part is
that this class is never used in the code (it appears just in a couple
of commented lines...)
--
Filippo
Re: error: compiler message file broken:
Posted by Manu George <ma...@gmail.com>.
Hi Jacek/Filippo,
I am also getting this error now with a fresh checkout.
Doing a google search gives some info that it is an error in the java
compiler.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6295912
and though not in same version
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6229540
But the reason this is ocurring now is a mystery. If i make a guess, I
can say that there are some new code blocks being executed during
compilation in the compiler now and the error is in these code blocks.
So it may be due to some changes in the openejb-core module.
Thanks
Manu
On 12/2/06, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
> On 12/2/06, Filippo Diotalevi <fi...@gmail.com> wrote:
> > > What compiler do you use? I have never seen a compilation error like
> > > this? Could you run M2 with -e (or even -X) command line option?
> >
> > Hi, these are the details:
> > java -version
> > java version "1.5.0_06"
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
> > Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)
>
> Huh? It's Sun JVM? I'm using it too. The error message is pretty
> strange (as they used to be, didn't they? ;-)). Do you happen to use
> Cygwin?
>
> It's just a guess, but could you move your directory from
> /home/fdiotalevi/workspaces/openejb3 into /openejb3.
>
> Give it a shot again after the change.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.jaceklaskowski.pl
>
Re: error: compiler message file broken:
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 12/2/06, Filippo Diotalevi <fi...@gmail.com> wrote:
> > What compiler do you use? I have never seen a compilation error like
> > this? Could you run M2 with -e (or even -X) command line option?
>
> Hi, these are the details:
> java -version
> java version "1.5.0_06"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)
Huh? It's Sun JVM? I'm using it too. The error message is pretty
strange (as they used to be, didn't they? ;-)). Do you happen to use
Cygwin?
It's just a guess, but could you move your directory from
/home/fdiotalevi/workspaces/openejb3 into /openejb3.
Give it a shot again after the change.
Jacek
--
Jacek Laskowski
http://www.jaceklaskowski.pl
Re: error: compiler message file broken:
Posted by Filippo Diotalevi <fi...@gmail.com>.
> What compiler do you use? I have never seen a compilation error like
> this? Could you run M2 with -e (or even -X) command line option?
Hi, these are the details:
java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)
The stacktrace is
Compiling 572 source files to
/home/fdiotalevi/workspaces/openejb3/container/openejb-core/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
error: compiler message file broken: key=compiler.err.file
org/apache/geronimo/kernel/Kernel.class not found arguments={0}, {1},
{2}, {3}, {4}, {5}, {6}, {7}
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Compilation failure
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.CompilationFailureException:
Compilation failure
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 22 seconds
[INFO] Finished at: Sat Dec 02 17:05:52 CET 2006
[INFO] Final Memory: 23M/55M
Re: error: compiler message file broken:
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 12/2/06, Filippo Diotalevi <fi...@gmail.com> wrote:
> Hi, I've just came back after a couple of days out of town,
> synchronized the trunk,
> mvn clean install
> and....
>
> [INFO] [compiler:compile]
> Compiling 572 source files to
> /home/fdiotalevi/workspaces/openejb3/container/openejb-core/target/classes
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> error: compiler message file broken: key=compiler.err.file
> org/apache/geronimo/kernel/Kernel.class not found arguments={0}, {1},
> {2}, {3}, {4}, {5}, {6}, {7}
What compiler do you use? I have never seen a compilation error like
this? Could you run M2 with -e (or even -X) command line option?
svn status // make sure no entries M or ? appear
mvn -e clean install
Send the error stack trace here if you don't sort it out yourself.
Jacek
--
Jacek Laskowski
http://www.jaceklaskowski.pl