Brian E. Fox wrote:
> I think we've gone way off the rails here. I see there's a proposal but
> haven't reviewed it yet.
>
> The first portion of this discussion was rather small in scope:
> Currently default executions of plugins have a null id. The null is used
> to indicate the default config for a plugin across all executions AND is
> used for lifecycle bound or plugins run on the cli. I think we simply
> should start by separating this. Keep default to replace the current
> null values for the global plugin configuration as it applies across all
> executions. Then define an id for the lifecycle and cli invocations to
> be applied to tweak the values as needed (but keeping default to apply
> across all). Going beyond this into multifaceted ids for packages etc is
> far too complicated imo.
Leads to
<executions>
<execution>
<goals>
<goal>testCompile</goal>
</goals>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</execution>
</executions>
<configuration>
<source>1.4</source>
<target>1.4</target>
</configuration>
Right ?
Completely hides the lifecycle from the user and removes the need of
redundant mojo parameters. Minimal input required from the user - Maven
just does the right thing. At least for this concrete example.
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
