On 4/11/07, Barrie Treloar <[EMAIL PROTECTED]> wrote:
On 4/12/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> I think every maven release should use a defined set of plugin
> versions. That would be reproducible and close to what it's happening
> now.
>
> Making the user list all plugins it's gonna be killer for newbies.
If I need a specific version (usual to workaround a known issue) then
I specify it in the the pom. Otherwise I want the latest.
and that was already identified as a problem with the current
implementation. I get the latest today and somebody else gets the
latest in two months, unless you run mvn -U
For snapshot builds if I will use specified, then latest.
For a released build, I want the pom to be transformed and fully
locked down so that the build is reproducible. And I don't want to do
that manually.
that sounds good idea too, but we can only do it for the default
lifecycle, we can't lock down all possible plugins out there
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
