[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] Calling JavaProjectConfigurator.configure() in m2e 1.6
|
Don't know off the top of my head, sorry. Secondary configurators were introduced to support m2e/wtp integration and I think jbosstools uses them too. Maybe check how this works there.
On Tue, Jun 23, 2015, at 12:47 PM, Csaba Kozák wrote:
Yeah, Android projects currently used that.
But our configurator is not called at all when declared as secondary to javaConfigurator. :S
Do android plugins use maven-compiler-plugin with compilerId=java? Java configuration should be automatically enabled for such projects already, no need to enable it explicitly.
On Tue, Jun 23, 2015, at 12:34 PM, Csaba Kozák wrote:
Thanks for the quick answer! I added:
<configurator
class="me.gladwell.eclipse.m2e.inject.GuiceExtensionFactory:me.gladwell.eclipse.m2e.android.AndroidMavenProjectConfigurator"
id="me.gladwell.eclipse.m2e.android.androidDevelopmentToolsProjectConfigurator"
name="Android Development Tools Project Configurator"
secondaryTo="org.eclipse.m2e.jdt.javaConfigurator">
</configurator>
However our configurator was not called at all due to this. Do i need to add a lifecycle mapping to the compiler plugin as well?
_______________________________________________
m2e-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
_______________________________________________
m2e-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
_______________________________________________
m2e-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
