lifecycle with version lock and default configuration of plugins

[Raphaël Piéroni <ra...@gmail.com>]

Hi folks,

In a plugin, i create a lifecycle (in lifecycle.xml) in which i managed
to call a specific goal in another plugin (appassembler) with some
configuration and without locking that plugin version.

In another plugin, i defined a new packaging (in componenet.xml),
in which i manage to call the same goal with locking the version
and without being able to define a configuration.

Is there a way to merge the two approaches?

My aim is to define a new packaging, creating mojos only for the
glue between external plugins and providing sensible default for
those. With locking the external plugins versions in the packaging
and leaving the pom free from default values (which are defaults in
the way the packaging uses the external plugins, but not default
for the average usage of these plugins).

Regards,

Raphaël

Re: lifecycle with version lock and default configuration of plugins

[Raphaël Piéroni <ra...@gmail.com>]

Any thoughs

Raphaël

2008/6/24 Raphaël Piéroni <ra...@gmail.com>:
> Hi folks,
>
> In a plugin, i create a lifecycle (in lifecycle.xml) in which i managed
> to call a specific goal in another plugin (appassembler) with some
> configuration and without locking that plugin version.
>
> In another plugin, i defined a new packaging (in componenet.xml),
> in which i manage to call the same goal with locking the version
> and without being able to define a configuration.
>
> Is there a way to merge the two approaches?
>
> My aim is to define a new packaging, creating mojos only for the
> glue between external plugins and providing sensible default for
> those. With locking the external plugins versions in the packaging
> and leaving the pom free from default values (which are defaults in
> the way the packaging uses the external plugins, but not default
> for the average usage of these plugins).
>
> Regards,
>
> Raphaël
>