Re: [m2e-dev] Alternative maven-compiler-plugin plugins?

[Benson Margulies <bimargulies@xxxxxxxxx>]

OK, I didn't follow the logic of the previous email, now I'm less confused.

On Tue, May 31, 2011 at 1:44 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> We already have such an extension point. As I tried to explain in [1],
> m2e jdt configuration is supposed to be reusable and extensible. You can
> either map the new groovy compilerId to existing
> org.eclipse.m2e.jdt.javaConfigurator project configurator provided by
> m2e.jdt or define new project configurator as subclass of
> AbstractJavaProjectConfigurator and map the new groovy compiler to it.
>
> [1] http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00616.html
>
> --
> Regards,
> Igor
>
> On 11-05-31 1:28 PM, Benson Margulies wrote:
>>
>> Recent email noted that the stock m2e support for the
>> maven-compiler-plugin runs away if the compilerId is not javac. This
>> strikes me as a bit ironic in the presence of the eclipse alternative
>> -- someone who has gone to the trouble to use the eclipse compiler
>> inside maven will be turned away empty-handed if they then try to use
>> m2eclipse.
>>
>> On another front, the groovy people are releasing an alternative
>> plugin which, if I understand it, causes the maven-compiler-plugin to
>> compile both java and groovy. All they need in a configurator is to
>> add the Groovy project nature on top of what m2e would usually do for
>> a vanilla java project.
>>
>> It would seem as if it would be good to have an extension point?
>> somewhere to declare: 'The XXX compilerId is compatible with the javac
>> compilerId ... oh, and by the way, also please run this here
>> configurator class'
>> _______________________________________________
>> m2e-dev mailing list
>> m2e-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>