[m2e-dev] m2e 0.13 - can't import anything anymore :(

[Max Rydahl Andersen <max.andersen@xxxxxxxxxx>]

Hi,

So i'm trying out 0.13 from https://repository.sonatype.org/content/sites/forge-sites/m2e/0.13.0/N/0.13.0.201103080404/
and I found some issues that before I open jiras would like to understand if this is really intended or not ?

First off, trying to import mavenprojects to eclipse:

Importing hibernatetools trunk - works in pre-0.13 and imports in seconds (assuming all dependencies already locally in maven).
In 0.13 it spends *alot* of time analyzing p2 repositories (not sure if it tests *all* sites or some specific ones but after 2 minutes I cancelled it).
And now it shows a page saying some of the pom.xml constructs aren't covered, build-helper, properties-maven, build-helper and maven-antrun-plugin.
All commonly occurring maven plugins.

And I cannot import this project ... even though m2eclipse would be able to configure all the dependencies, setup the java classpath etc. and my project would
work fine.

Is this really where we are going with m2eclipse in the end ? 

Is there anything users can do to have m2eclipse ignore the parts it doesn't understand instead of just not 
allowing import.

I've also tried importing other existing maven projects I have on my disk and I didn't find a single one I could actually import
since they used build-helper, maven-antrun-plugin or other plugins there aren't a specific m2eclipse plugin for yet.

None of them which m2eclipse would actually *need* to setup anyway for the project to be usable from within the IDE.

Here are the list of maven projects i've tried so far - btw. the egit was different in the sense that it simply wouldn't let me import because
I didn't have maven-deploy-plugin in my local repo - something I could do in 0.12 as far as my testing goes.

hibernatetools: https://svn.jboss.org/repos/hibernate/tools/trunk
as7: https://github.com/jbossas/jboss-as
Shrinkwrap: https://github.com/shrinkwrap/shrinkwrap
Seam modules such as: https://github.com/seam/mail
Egit: git://egit.eclipse.org/egit.git  

This basically makes m2eclipse useless for anything but the cleanest  maven projects...I'm worried about this trend since
it basically removes the reason why maven got adopted (good eclipse and intellij support - even for framework dev projects)

With all these (done by very different teams) not being able to import and afraid to start looking at "normal" project examples ;)

I still do not understand why those lifecycles not supported won't just be a big warning sign and just not be executed !?

With the current approach of *requiring* specific eclipse plugins for a maven plugin will stiffle the adoption of maven IMO.
i.e. who is going to provide a eclipse plugin for some small maven plugin that are helping for a specific thing that is not
even necessarily covered by eclipse ? i.e. building docbooks. ...and how about plugins which you as a user does not want
to install matching plugins since it drags in functionality you do not want exposed in the IDE ?

I've seen mentions of users being able to add something in their pom's to have m2eclipse ignore their setups but
haven't been able to find docs about this (https://docs.sonatype.org/display/M2ECLIPSE/Project+build+lifecycle+mapping seems close
but just talks about ideas, but nothing specific)

Wondering if the import wizard could provide support for adding those elements/configuration to allow import to occur.
...and then if that is doable - why not provide a way to have that be the default for unmmapped elements when no match found.

/max
http://about.me/maxandersen