ssage -
From: "Barrie Treloar"
To: "Maven Users List"
Sent: Friday, July 27, 2012 12:29:04 AM
Subject: Re: JDT compiler compliance level as a parameter for eclipse:eclipse
target of maven-eclipse-plugin
On Fri, Jul 27, 2012 at 7:57 AM, Barrie Treloar wrote:
> On Fri,
On Fri, Jul 27, 2012 at 7:57 AM, Barrie Treloar wrote:
> On Fri, Jul 27, 2012 at 7:13 AM, Wayne Fay wrote:
>>> Long story short, I tried to modify eclipse project generation so that
>>> in the .settings/org.eclipse.jdt.core.prefs instead of this:
>>> org.eclipse.jdt.core.compiler.compliance=1
On Fri, Jul 27, 2012 at 7:13 AM, Wayne Fay wrote:
>> Long story short, I tried to modify eclipse project generation so that
>> in the .settings/org.eclipse.jdt.core.prefs instead of this:
>> org.eclipse.jdt.core.compiler.compliance=1.5
>> I get this (look at the compliance):
>> org.eclipse
> Long story short, I tried to modify eclipse project generation so that
> in the .settings/org.eclipse.jdt.core.prefs instead of this:
> org.eclipse.jdt.core.compiler.compliance=1.5
> I get this (look at the compliance):
> org.eclipse.jdt.core.compiler.compliance=1.6
> but didn't find a wa
Hi,
I've tried to checkout Jenkins CI source code and generate an Eclipse project
for it (see instructions in [1]). Unfortunately generated Eclipse projects
seemed to contain errors, which I first reported as a Jenkins bug [2]. Further
investigation revealed that even though Jenkins is build wi
