You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Non standard compilerIds for the maven-compiler-plugin are unknown to m2e and thus require a specific lifecycle mapping to enable Java support in Eclipse (see m2e-jdt-compiler)
I think we should, rather than embed new bundles (m2e-jdt-compiler and another for google's error-prone), simply embed our own default lifecycle-mapping-metadata.xml (for commonly used maven plugins)
The text was updated successfully, but these errors were encountered:
as a consequence, lifecycle mappings for non standard maven compilerIds can be removed.
Effectively reverting changes for #196
Signed-off-by: Fred Bricon <fbricon@gmail.com>
Non standard compilerIds for the maven-compiler-plugin are unknown to m2e and thus require a specific lifecycle mapping to enable Java support in Eclipse (see m2e-jdt-compiler)
I think we should, rather than embed new bundles (m2e-jdt-compiler and another for google's error-prone), simply embed our own default lifecycle-mapping-metadata.xml (for commonly used maven plugins)
The text was updated successfully, but these errors were encountered: