[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] code style guidelines?
|
Any code contrib needs to come from a bug report.
If the patch is longer than 200 lines of code, we will need to put the contrib through the IP process, but don't worry this is lightweight.
On 2010-12-26, at 1:53 PM, Igor Fedorenko wrote:
> m2e projects have jdt code formatter and templates configuration,
> ctrl-shift-f should format sources for your.
>
> Please note that you need to use m2e sources from git.eclipse.org as
> explained in m2e dev guide [1]. I also believe that all non-committer
> code contributions should go though eclipse bugzilla, but I need to
> double-check this.
>
> [1] https://docs.sonatype.org/display/M2ECLIPSE/Developer+Guide
>
> --
> Regards,
> Igor
>
> On 10-12-26 12:51 PM, Andreas Höhmann wrote:
>> hihi,
>>
>> I would like to contribute some code (re-factoring, documentation ...)
>> to the m2e project ....
>> I got the code running :) But what code guidelines (code formatter,
>> checkstyle etc.) would be used for m2e?
>>
>> Regards
>> Andreas
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
