Re: [m2e-dev] Testing Lifecycle Contributions

[David Carver <d_a_carver@xxxxxxxxx>]

I found part of the problem.  If a PluginManagement configuration is 
included in the POM file, it takes prescedence over the eclipse plugin 
contributed configuration.   This causes the eclipse configuration 
contribution to never execute.

Dave

On 06/27/2011 12:06 PM, David Carver wrote:
> I'm setting up a unit test based on the code and tests I found for the 
> Antlr example in the m2e-core-tests package.   As far as I can tell I 
> have everything setup right.  Will report back here with some results.
>
> Dave
>
> On 06/27/2011 01:52 AM, Igor Fedorenko wrote:
> > m2e is expected to find lifecycle mapping configuration contributed by
> > any installed eclipse plugin, regardless installation method (via m2e
> > discover, p2 installable ui, etc). I am not aware of any problems in
> > this area, so please double check that your eclipse installable actually
> > includes all required plugins and their dependencies.
> >
> > Also, [1] has more detailed explanation how different pieces fit 
> > together.
> >
> > [1] http://wiki.eclipse.org/M2E_Extension_Development
> >
> >
> > --
> > Regards,
> > Igor
> >
> > On 11-06-24 6:26 PM, David Carver wrote:
> > > I'm working on updating the Turmeric SOA plugins to work with the just
> > > released m2e 1.0.0. I'm running into some problems in testing the
> > > updated configuration and lifecycle mapping contributions.
> > >
> > > When I create a LifeCycleMappingMetadata.xml file and just specify the
> > > action, the maven plugins run, but the generated-source folders don't
> > > get added as source folders. So, I added the <configurator> entry
> > > following the Antlr example. However, now when I import a project, the
> > > plugins are marked with an error, and it wants to go out to the
> > > discovery site to find them.
> > >
> > > It almost seems that unless the plugins are already installed in the
> > > target platform (which they should be because they are coming from the
> > > workspace during debugging, and launching the eclipse plugin for
> > > testing), then it can't seem to find them unless it's on the discovery
> > > site.
> > >
> > > What is the recommended way to test and debug a configuration.
> > >
> > > Dave
> > >
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev