Re: [m2e-dev] contribution guide

[Jeff MAURY <jeffmaury@xxxxxxxxxxxxx>]

Jan,

I agree there is no much documentation about M2E development.
However, I have found this bolg entry (http://intellectualcramps.wordpress.com/2011/07/01/developing-a-m2e-1-0-0-configuration-plugin/) that is very helpful.

Regards
Jeff

On Sun, Jul 10, 2011 at 2:26 PM, Jan Prach <jendap@xxxxxxxxx> wrote:

Hi,

is there some contribution guide?

There's not much on http://eclipse.org/m2e/developers/

No big document is needed. Just add a few details, please. Something like
1) What form shall a contribution have? A patch attached in bugzilla? Merge request at github? Push to some gerrit instance?
2) What about the code in github.com/sonatype? Bugs to git connector to github? There's no issueManagement section in git connector.

It's not just about m2e. It's more generic problem. "Maven" -> "Import Project(s) from SCM" is awesome! One can easily import the project, debug it, fix it, ... and then what?


Regards,
Jan


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

-- 
"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com

http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury