gistfile1.txt

#Moving m2e-wtp project to Eclipse

 Over the last 2+ years we have done a lot of work at helping improving Maven Integration for Eclipse (m2e) in areas of performance, features and extensions.

One of those extensions, if not the most important one, is maintaining and developing Maven Integration for Web Tools Platform also called m2e-wtp.

Today (or rather last night) our proposal for making this an Eclipse.org project [got posted](http://www.eclipse.org/proposals/technology.m2e.m2e-wtp/).

#What is m2e-wtp 

m2e-wtp is what helps you get seamless import of your maven projects with all the right dependencies configured, the proper assembly setup and it will even enable features in Eclipse that are relevant based on your maven pom.xml file, in context of the Web Tools Platform features : automatic configuration for Web, EJB, EAR, Connector, Web Fragment and Application Client projects. 

m2e-wtp also brings some maven exclusive features to your favorite IDE, such as dynamic [web resource filtering](http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html) or [war overlays](http://maven.apache.org/plugins/maven-war-plugin/overlays.html).

You can get the current m2e-wtp from [Eclipse Marketplace](http://marketplace.eclipse.org/node/96737) or by [installing JBoss Tools](www.jboss.org/tools/download).

#Why bring m2e-wtp to Eclipse

m2e-wtp have had a "fun" life over the years. After m2e moved to Eclipse, m2e-wtp was in a weird place seeing that Sonatype hosted the issue tracker and the main source repository at github while JBoss eventually took over the development and maintenance, but the core m2e was at Eclipse. 

This spread between multiple organizations have made it harder than necessary for potential contributors to get involved and it also made it tricky for users to know where and how to get involved and get help.

To remedy this, we've worked over the last couple of weeks/months to prepare a proposal to move m2e-wtp and this proposal is now what is [available on Eclipse.org]((http://www.eclipse.org/proposals/technology.m2e.m2e-wtp/)).

#What does this mean for JBoss Tools users ?

It should not have any big impact to start - we plan on making the migration from the original m2e-wtp to m2e-wtp at Eclipse as smooth as possible.

We will continue to drive and contribute to m2e-wtp, and JBoss Tools will still provide extensions and integration on top of m2e and m2e-wtp. Some of these extensions don't make sense elsewhere than in context of JBoss Tools and others will eventually find their way into m2e and m2e-wtp.

#How do I support/contribute to this proposal ?

If you are interested in this project and seeing it become a full eclipse project, please comment on it on [Eclipse Propsal forum](http://www.eclipse.org/forums/index.php?t=thread&frm_id=202) or email me directly at [[email protected]](mailto://[email protected]).

We would love to hear your thoughts on this, even if it is just a "that is about freaking time" comment :)

In conclusion I would like to thank Fred Bricon for his outstanding work on m2e-wtp and I'm looking forward to see where he will take it going forward hosted at eclipse.org.

Great thanks also go to all the people from Sonatype, IBM, Oracle, SAP, VMWare and others involved in making this proposal happen - to know about them and the proposal, read [more here](http://www.eclipse.org/proposals/technology.m2e.m2e-wtp/).

Thank you and have fun!