Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Wish to contribute an incubating bundle for easier import
I think Jason's suggestions makes good sense and should be done.

Since maven eclipse has a marker we can use then skipping maven import makes perfect sense to do in this case. 

Telling users to use the generic import in this case kinda defeats the whole point of easyimport. 

/max


On 13 Apr 2015, at 18:28, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On 04/13/2015 06:20 PM, Jason van Zyl wrote:
... I think a user would just expect the right thing to happen if they used the detection mechanism ...

Defining "the right thing" is the tricky part. IMO, if someone imports a Maven project, the right thing is to enable m2e anyway. Those that don't use it are relying on an anti-pattern and should have to adapt to usage of m2e. It's also the role of the IDE to enforce good practices.

I've examples of plugin projects that have a .project and a pom.xml committed, but that don't have m2e enabled in their project description. In that case, I find it good that the .project gets modified to enable m2e.
This use-case is somehow the opposite of the one you mentioned. Is there a way to make a distinction between both? If not, which one should drive we prefer to support? (as you understood, my opinion would go for simply ignoring the existence of maven-eclipse-plugin, but YMMV).
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev

Back to the top