org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT ignores maven-compiler-plugin

2009-04-23 Thread Davis Ford
Hi, I just enabled all snapshots for plugins, and a side effect of this was to pull down org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT version of eclipse plugin. Now, my project breaks in eclipse b/c it sets the JDK to be (I think) the system default (which is JDK 1.5), but my

Re: org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT ignores maven-compiler-plugin

2009-04-23 Thread Brian Fox
That's why we suggest locking down your plugin versions in your poms. Then you'll have controll over which ones you get as snapshots. See here for more info: http://www.sonatype.com/people/2008/04/maven-209-released/ The eclipse plugin does not seem to be one that has a default in the super

Re: org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT ignores maven-compiler-plugin

2009-04-23 Thread Barrie Treloar
On Fri, Apr 24, 2009 at 11:41 AM, Davis Ford davisf...@zenoconsulting.biz wrote: Hi, I just enabled all snapshots for plugins, and a side effect of this was to pull down org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT version of eclipse plugin. Now, my project breaks in eclipse

Re: org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT ignores maven-compiler-plugin

2009-04-23 Thread Davis Ford
My apologies Barrie...this is the con entry: classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ User error. Somehow my eclipse default JDK/JRE setting got switched back to JDK 5. When I refreshed using mvn eclipse:eclipse it resets the JDK back to default JRE_CONTAINER --

Re: org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT ignores maven-compiler-plugin

2009-04-23 Thread Barrie Treloar
On Fri, Apr 24, 2009 at 12:37 PM, Davis Ford davisf...@zenoconsulting.biz wrote: My apologies Barrie...this is the con entry: classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ User error.  Somehow my eclipse default JDK/JRE setting got switched back to JDK 5.  When I