I think it's the m2eclipse plugin picking up the compiler
settings from here?:
http://anonsvn.jboss.org/repos/jbossas/trunk/pom.xml
I haven't tried changing those settings and then re-importing the
project to confirm it though.
On Thu, 2010-01-28 at 08:57 -0600, Brian Stansberry wrote:
AS 6 requires JDK 6 so there's no reason to specify JDK 5 for
these
modules. No one should be trying to work on trunk w/ a workspace default
of JDK 1.4, so I can't see any harm in your change.
My guess is some time back in the days of the 1.4 to 5 transition
someone had 1.4 as their eclipse default, changed these to temporarily
deal with some local issue, and then it got inadvertently committed.
On 01/28/2010 05:24 AM, Kabir Khan wrote:
> Is there any reason why the .classpath files for cluster, varia and server are
J2SE-1.5? I get loads of errors with those, but if I edit those and set them to the
"workspace default" everything compiles, e.g.
>
> --- server/.classpath (revision 100034)
> +++ server/.classpath (working copy)
> @@ -2,7 +2,7 @@
> <classpath>
> <classpathentry kind="src" output="target/classes"
path="src/main/java"/>
> <classpathentry kind="src"
path="target/generated-sources/javacc"/>
> - <classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
> <classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
> + <classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> <classpathentry kind="output" path="target/classes"/>
> </classpath>
>
> Before I commit I want to make sure this is not just a local problem
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss by Redhat
xxxxxxxxxxxxxxxxxxxxx