[m2e-dev] New lifecycle mapping for axistools-maven-plugin

["Thorsten Heit" <thorsten.heit@xxxxxx>]

Hello to all,

after reading m2e-users for quite some
time now and lots of discussions there about lifecycle mappings in the
new version of m2e, I just joined this discussion list and first I'd like
to introduce myself:

My name is Thorsten Heit. I'm a software
engineer working at an insurance company located at Saarbrücken, Germany.
I'm using the m2e plugin since, I guess, at least version 0.10. At work
I'm using org.codehaus.mojo:axistools-m-p more or less often to generate
Java code from WSDLs. 

After having ugpraded to m2e 0.13 I
discovered that my pom.xml contained error markers and didn't work right
out-of-the-box anymore as before. After some googling I finally ended up
with a solution I described recently at m2e-users: http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00837.html

After Igor posted some links for the
extension development I recently started developing a plugin on my own
to get rid of my workaround and to provide a native lifecycle mapping for
that plugin. You can find the code at Github:
https://github.com/theit/m2e-lifecycle-axistools

As far as I can tell the plugin seems
to work on my machines: It automatically adds the folder containing the
generated sources to the Java build path, and recreates the files when
the WSDL(s) changes. I'd like to welcome everyone to test it and give some
feedback.

It's the first time ever I developed
an Eclipse so I hope everything is done right...


Before starting some questions, I'd
like to thank some people whose code I looked at to get insights in writing
a m2e extension:
- Benson Margulies for his Checkstyle
and PMD plugins
- Christian Schneider for his CXF code
generator plugin
- and all the guys at Sonatype who made
all this possible :-)


Some questions:
- Actually I'm using org.eclipse.m2e.axistools
as package name and the Eclipse EPL as license. Is that ok? Do you suggest
something better/else/...?
- If you think the plugin is ok, what
are the next steps to make it available in the m2e marketplace?


Greetings

Thorsten