On Sun, Jan 10, 2010 at 2:48 PM, Brett Porter <br...@apache.org> wrote:
> > What is the original use case that led to the bug? I'm wondering if it is > sane and needs the runtime info, or if it actually should have just the POM > as fully resolved from the repo. > > Cheers, > Brett > > The code involved is at line 1797 in > EclipsePlugin.java<http://svn.apache.org/viewvc/maven/plugins/tags/maven-eclipse-plugin-2.7/src/main/java/org/apache/maven/plugin/eclipse/EclipsePlugin.java?view=markup>. > The issue was opened in response to http://jira.codehaus.org/browse/MECLIPSE-633 . The plugin code is kinda suspect as I'm not quite sure why the EclipseMojo just can't rely on the injected parameter it is looking for rather than parsing its Xpp3Dom directly - guessing as some previous bug work around? Still, I don't think the project model should change this drastically unless there is a good reason and it is well documented. Meanwhile Jason is pushing for a release of the eclipse plugin and until we reach a consensus on what to do then maven-eclipse-plugin will remain not passing integration tests for maven 3. -Peter
