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 pom.

On 4/23/2009 10:11 PM, Davis Ford 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 b/c it sets the JDK to be (I think)
the system default (which is JDK 1.5), but my maven-compiler-plugin
settings in the pom specify 1.6.  So maven compiles the sources, and
when I launch the project in eclipse, it throws an error saying the
class version is wrong.

Nothing very interesting in the config below.  This problem did not
exist for me until I just opened up plugin snapshots -- which I think
I'll turn off.  This is on:
$ mvn -version
Maven version: 2.0.9
Java version: 1.6.0_07
OS name: "mac os x" version: "10.5.6" arch: "x86_64" Family: "mac"



<plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-eclipse-plugin</artifactId>
                                <configuration>
                                        <downloadSources>true</downloadSources>
                                        
<downloadJavadocs>true</downloadJavadocs>
                                </configuration>
                        </plugin>

<plugin>
                                <artifactId>maven-compiler-plugin</artifactId>
                                <configuration>
                                        <source>1.6</source>
                                        <target>1.6</target>
                                </configuration>
                        </plugin>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to