Compile directly with javac, set your classpath manually with -cp, and
use -verbose so you know what class (and line?) it quits on. Its also
possible (likely?) that a similar verbose setting may exist in plexus
compiler, but I'm just not sure and I haven't looked, so you might be
able to get the sa
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) jus
Michael Mehrle schrieb:
> I am suddenly experiencing a strange error when compiling my project (see
> stack trace below) - the maven compile plugin crashes and then refers to
> some compiler error which cannot be parced. It even asks me to submit a bug
> report with the JDC - never encountered anyt
On Mon, Feb 25, 2008 at 6:27 PM, Michael Mehrle <[EMAIL PROTECTED]> wrote:
> I am suddenly experiencing a strange error when compiling my project (see
> stack trace below) - the maven compile plugin crashes and then refers to
> some compiler error which cannot be parced. It even asks me to submi
I am suddenly experiencing a strange error when compiling my project (see
stack trace below) - the maven compile plugin crashes and then refers to
some compiler error which cannot be parced. It even asks me to submit a bug
report with the JDC - never encountered anything like this in 12 years of
Ja
