As mentioned before I'm not a big fan of merging these plugins. IMO,
SHITTY provides a lot of additional functionality on top of what the
maven-invoker-plugin provides, like:
* Groovy integration
* More flexible configuration
* Clean and install support integrated (for less pom.xml
conf
Done : http://jira.codehaus.org/browse/MPLUGIN-67
Thx
Arnaud
On Jan 21, 2008 8:11 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Arnaud HERITIER wrote:
> > Hi Team,
> >
> > Can we add in each announcement of a plugin (or library) the minimum
> > version of maven required to use it.
>
> +1
>
Arnaud HERITIER wrote:
Hi Team,
Can we add in each announcement of a plugin (or library) the minimum
version of maven required to use it.
+1
Excellent idea.
For each new release of a plugin I have to test it with our maven 2.0.5 to
see if it is compatible (which isn't the case for the ja
Hi Team,
Can we add in each announcement of a plugin (or library) the minimum
version of maven required to use it.
For each new release of a plugin I have to test it with our maven 2.0.5 to
see if it is compatible (which isn't the case for the jar plugin 2.2 for
example).
Couldn't we automat
Thanks but I have a hard time understanding this to be the fundamental
failure mode.
I have verified that for all build plugins (except site) we use fixed
versions. (Although we give up automatic updates by doing this what we gain
is repeatable builds where plugins used are always the same.)
