Paul, Sorry, I forgot to make it yesterday. Now I have the problem that I cannot reproduce it.
The problem appeared last week when I updated in one sequence from Maven 2.0.7 to 2.0.8 and the latest versions of m2eclipse and Q4E in two different instances of Eclipse. After seen the problem I set up from scratch twice Java 6 and Eclipse with the plugins and I thought I deleted all possible influences, but it did not work. In the morning, I installed Java 1.5/ 12 and it went well. After your mail, I switched JAVA_HOME back to 6.0.03 and the problem disappeared. Strange!! It looks like that updating either m2eclipse or Q4E from previous versions caused the problem. When I sent the mail, it looked like problem with 6.0.03. My guess is, that m2eclipse switch to an internal version of Maven 2.1 caused the problem, but I can not prove it. I have a copy of the situation of yesterday on my private PC at home, when I am back from travel I try to get the stack trace. This may last until Monday. regards Holger Sachse Würth Phoenix S.r.l. Holger Sachse Via Kravogl 4 I-39100 Bolzano Direct: +39 0471 56 40 16 Mobile: +39 335 6 19 24 74 Fax: +39 0471 56 41 22 E-Mail: [EMAIL PROTECTED] Website: www.wuerth-phoenix.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Benedict Sent: Wednesday, December 12, 2007 14:47 To: Maven Users List Subject: Re: Maven and Java 6 Patch 3 Provide a stack trace please. On Dec 12, 2007 7:45 AM, Sachse, Holger <[EMAIL PROTECTED]> wrote: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
