Re: [m2e-dev] Secondary "Lifecycle mapping" for m2eclipse in indigo ?

[Vlad Tatavu <vtatavu@xxxxxxxxxxxx>]

Did u declare your project configurator(s) as secondary to another 
configurator in plugin.xml?

Here's how one of those secondary configurators (in the example u 
mentioned) is declared in plugin.xml:

<configurator
            
class="org.eclipse.m2e.tests.configurators.TestProjectConfigurator"
            id="org.eclipse.m2e.configurator.testsecondary"
            name="TEST_SECONDARY"
            secondaryTo="org.eclipse.m2e.configurator.test">
</configurator>

Vlad

On 3/9/2011 3:29 PM, Snjezana Peco wrote:
> The following is a simple example:
> It is necessary to add secondary project configurator for wtp or jdt 
> configurator to a new plugin.
> When I define secondary configurator without lifecycle mapping, it is 
> ignored. If I add lifecycle mapping (for the compile or war plugin), 
> m2e returns the "Duplicate lifecycle mapping metadata for ...". error. 
> What is the real way to add secondary configurator? I believe that 
> secondary project configurator doesn't need lifecycle mapping because 
> lifecycle mapping is defined in the primary configurator.
> The examples in  
> https://github.com/sonatype/m2e-core-tests/tree/master/org.eclipse.m2e.tests/projects/lifecyclemapping/secondaryConfigurators 
> define primary and secondary configurators in the same lifecycle 
> mapping and doesn't help here.
>
> Snjeza
>
> Igor Fedorenko wrote:
> > I think I understand the problem, but a sample project with explanation
> > of what should be activated based on what condition and in what order
> > will be useful here.
> >
> > Bugzilla is probably a good place to provide this problem as I may
> > forget about it otherwise ;-)
> >
> > --
> > Regards,
> > Igor
> >
> > On 11-03-09 07:07 AM, Max Rydahl Andersen wrote:
> > > On Mar 9, 2011, at 13:03, Snjezana Peco wrote:
> > >
> > > > Hello,
> > > >
> > > > I would like to know if it is possible to set a priority if there 
> > > > are several secondary configurators placed in different Eclipse 
> > > > plugins that are independent of each other?
> > >
> > > I guess what you mean Snjeza is that there are configurators that 
> > > makes decisions based on what is already configured.
> > >
> > > For example for Seam we enable the core seam functionality and if 
> > > JSF is also enabled on the project we enable additional things; 
> > > thust JSF is not a hard requirement
> > > but if it is on the project the Seam configurator should be invoked 
> > > *after* the JSF one.
> > >
> > > /max
> > >
> > > > Thanks,
> > > > Snjeza
> > > >
> > > >
> > > > Max Rydahl Andersen wrote:
> > > > > > AFAIK, Igor finished implementing support for secondary project 
> > > > > > configurators.  I think the only examples we have are in these 
> > > > > > unit tests:
> > > > > >
> > > > > > https://github.com/sonatype/m2e-core-tests/tree/master/org.eclipse.m2e.tests/projects/lifecyclemapping/secondaryConfigurators 
> > > > >
> > > > > These all look to be configurators that gets explicitly written 
> > > > > and hooked into users pom files - got an example or point me in 
> > > > > the direction of how
> > > > > these gets invoked on any projects to see if they are applicable ?
> > > > >
> > > > > /max
> > > > >
> > > > >
> > > > > > Vlad
> > > > > >
> > > > > > On 3/8/2011 5:07 AM, Max Rydahl Andersen wrote:
> > > > > >
> > > > > > > Hi Igor,
> > > > > > >
> > > > > > > What's the status on the "secondary" configurators as outlined 
> > > > > > > at http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg00169.html ?
> > > > > > >
> > > > > > > We've finally released JBoss Tools 3.2 so can start looking more 
> > > > > > > actively into Indigo/m2eclipse migration now so
> > > > > > > looking for pointers/examples to get started ;)
> > > > > > >
> > > > > > > /max
> > > > > > > http://about.me/maxandersen
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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
> > > > >
> > > > > /max
> > > > > http://about.me/maxandersen
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > m2e-dev mailing list
> > > > > m2e-dev@xxxxxxxxxxx
> > > > > https://dev.eclipse.org/mailman/listinfo/m2e-dev
> > >
> > > /max
> > > http://about.me/maxandersen
> > >
> > >
> > >
> > > _______________________________________________
> > > 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