On 11 Apr 07, at 1:04 PM 11 Apr 07, Brett Porter wrote:
I think it's more complicated than just removing that.
Firstly, large numbers of command line plugins will stop working.
For anything specified in POM the version needs to be specified.
Anything that is useful and required for a build it should be
specified in the POM. For tools like the IDE file generators and
Archetype defaulting to the latest version isn't going to screw up
anyone's build but it might screw up some infrastructure tooling. If
this was so inconvenient for users then that's fine but even not
specifying the version of a tool could cause problems and if we
provide an easy way to find versions users can specify them. I still
don't know if defaulting for tool plugins is good, but it's
definitely not good for anything you actually need to make your build
work.
Secondly, we need to provide a solution for implied plugins (we can
set the version in the lifecycle and then let the user give
pluginManagement to override it, but I'd like to see plugin 'packs'
as a better solution to reduce the amount of configuration needed).
The equivalent of what Brian did for dependencyManagement would work
well for plugin configurations.
Thirdly, we need to think carefully about the impact on existing
builds. We're not just impacting the people that wrote the build -
we impact the random people that grab a project and unwittingly try
and build it with 2.1 not knowing the author never tested that, and
get the bad experience.
The model of the POM will be different where the schema and validator
would change to have a version be mandatory. Along with 2.1 users are
going to get a new model version so we can figure out what's best to
do given a mismatch: point people to the new tool to detect
configuration problems with versions or something else. People will
have to consciously move to the new model.
I'm still in favour of a compatibility mode that can be driven by
the prerequisites or the modelVersion. I say let people use the
dependency plugin now to start fixing their builds, but for 2.1 let
them make the conscious decision to move up to this.
- Brett
On 12/04/2007, at 2:54 AM, John Casey wrote:
Hi everyone,
I'd like to make sure we're all on the same page with the plugin
auto-version resolution stuff that we've been discussing lately
(on the
assembly-plugin vote thread, for one thing). I think it's clear
that we
cannot continue to allow Maven to resolve RELEASE or LATEST meta-
versions
for plugins any more. I'd actually argue that this is bad practice
for ANY
artifact that is to be resolved, including site skins, etc. since
it kills
our ability to deprecate features.
I'd like to completely remove this from the DefaultPluginManager
in trunk,
so we can start moving away from this practice immediately.
I guess this is an informal vote on the subject, but I wanted to get
everyone's opinions before I move on it, since it's a fairly
important
change.
Here's my +1.
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
