That makes sense actually - thanks. However, it doesn't give me much hope...
Question: how were you able to find the piece of code that was triggering
this error? We have a mixed dev environment and it's pretty unrealistic that
everyone is going to update their JDK (and to do it on our servers) just to
fix that one piece of code that breaks an entire build?
I know this is not maven specific and this is my last post on this - if
anyone has any ideas on how to narrow down what breaks the compiler I'd
REALLY appreciate ;-)
Michael
On Mon, Feb 25, 2008 at 11:54 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
>
> Eclipse does not compile code using Sun's compiler ("javac"); it has its
> own entirely separate compiler implementation. It does not provide its
> own JVM ("java") or java-standard-library implementation (rt.jar etc).
>
> So it is no surprise to find that eclipse's compiler works where the sun
> java compiler crashes (and vice versa).
>
> This is just a sun javac bug that your code has triggered, and nothing
> to do with Maven. This has happened to me half-a-dozen times in
> half-a-dozen years.
>
> See: http://en.wikipedia.org/wiki/Java_compiler
>
> Regards, Simon
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
