Starting to get somewhere. Running mvn in debug mode so I can attach eclipse to the running instance. One thing I am noticing is that the attached sources don't match exactly what is being run by maven. The eclipse plugin defines the dependency on version 2.0.1 but I think the version being used is 2.0.4 (which would make sense since mvn -version is 2.0.4), so that would mean that the dependency section in the Mojo is for compilation only and not used at runtime.
Anyway, after browsing through stack traces I eventually get to the fact that the pluginDescriptor has a value of "test" and looking at the source file (which is the installed jar) I can see that the version is "test" in my installed plugin. <eclipse-jar>!/META-INF/maven/plugin.xml <plugin> <description>Internal release from subversion revision r485327. Applied patches: * http://jira.codehaus.org/browse/MECLIPSE-206 * parent version now 4 instead of 4-SNAPSHOT</description> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-eclipse-plugin</artifactId> <version>test</version> Now how did that happen? My pom version is: <version>2.3-INTERNAL-r485327-pMECLIPSE-206</version> Maybe the bug is in install... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
