I'm having trouble getting m2e to invoke my maven code generating plugin[1].
I've rewritten it to use BuildContext per [2] and I set up the
lifecycle-mapping-metadata.xml [3].
With that, Eclipse complains about a demo project that includes the
plugin when I install a snapshot with syntax errors i
Hi,
Yes, I had tried doing Maven -> Update Project (more than a few times). I had
not updated any Eclipse or m2e config manually. I had installed the YEdit
plugin.
In between sending my last email and receing yours, I reinstalled Eclipse and
now am on Version: Neon.1 Release (4.6.1). This s
You can see how m2e "maps" your plugin execution to Eclipse workspace
build in project properties, under Maven, Lifecycle Mapping. Check that
it says mapping=execute and source=maven-plugin there. You can also
enable debug log and see if m2e logs anything interesting in
.metadata/.plugins/org.eclip
On Tue, Oct 4, 2016 at 4:41 PM, Igor Fedorenko wrote:
> source=workspace means the plugin is ignored at workspace level, most
> likely you used quick-fix to do that some time in the past. You can see
> workspace-level configuration in Eclipse Preferences, Maven, Lifecycle
> Mapping ("basic" is a