Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Another lifecycle-ish feature

'resolve the config' API is only going to work for plugins bound to
project execution plan. You'd have to extract configuration from
pluginManamagement in your code, but this probably means one or two
extra lines.

--
Regards,
Igor

On 11-01-25 06:01 PM, Benson Margulies wrote:
On Tue, Jan 25, 2011 at 5:56 PM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>  wrote:
Short answer, no plans to provide direct support for this in m2e 1.0

I'm not surprised here, I get it.


Longer answer, you probably need to look inside site:site configuration,
find out what reporting plugins are configured, then look inside
<pluginManagement/>  to find reporting plugins' configuration.

And once the 'resolve the config' API is available, that's not going
to be terribly difficult.


We still need to figure out how m2e is going to activate your project
configurator. One possibility is to allow mapping goals from site and
clean lifecycles to trigger activation of project configurators. I think
this should be relatively straightforward change, but I am not sure
about performance implications.

That makes sense.


Any ideas and suggestions are welcome.

--
Regards,
Igor

On 11-01-25 05:44 PM, Benson Margulies wrote:

In M3,<reporting/>    is dead, replaced by a plugin list inside the
config of the site plugin.

I've determined by experiment that even constructing a lifecycle for
"site:site" does not give me the plugin executions from inside the
site plugin.

So, folks would like to propagate config from reporting plugins to
Eclipse plugins. Any ideas?
_______________________________________________
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


Back to the top