On 9-Feb-08, at 8:49 AM, Aaron Metzger wrote:
Brian E. Fox wrote:
We advertise the hell out of it and people will discover it as
they have a
problem that they resolve, can migrate to it as an upgrade process
in their
company environments and we don't screw someone over with our
benevolent
power.
I think the biggest beef people have is that we are unstable by
default. I don't think that requiring some action to get the
versions locked is really going to help much. Otherwise we just
continue to advertise the hell out of locking down your versions in
the pom (which hasn't been working).
--Brian
A tiny inexperienced voice from the user side of things chiming in
here...
For me, I am completely aware that I want to lock *everything* down
(including plugins) to have reproducible builds. So marketing,
advertising, pleading with us, educating us is not the issue.
The problem is not knowing or being able to keep up with the list of
what combination of plugins and maven versions work well together.
Whether or not the list of plugin versions is in the super POM is
not the isue for me. It is the wisdom and experience of the person
who would make the choices of which versions of the plugins to put
in that default list that is the real value.
In general I don't want to have to make those choices for every
plugin -- just the occasional exception for when I really need some
new feature or old compatibility.
Either of two approaches would satisfy me:
1) Benevolent dictators strongly suggest the list of plugin
versions which are thought to be stable together and that is in the
super POM or I just cut-n-paste the suggested list in there myself
from the web site.
The code in the enforcer plugin can actually extract the versions that
were used as part of a build so we could turn this into something
people could use. John has also been working on a lifecycle plugin
which displays the information about the lifecycle which means we
could extract the information from that too and make a descriptor. So
we can test different combinations of plugins as they are released and
give those combinations to users in some controlled way.
2) I just go ahead and try my build process using all the latest
plugin versions (current default behavior) and then when I see that
they all work together have some mechanism to freeze the list and
have the current versions (whatever they are) automatically written
into my POM without me having to sort through and figure out what
the versions are and manually insert them into the POM. I would
want to be able to freeze the list not just at release time but at
any arbitrary time to stabilize the development environment for my
team.
Thanks.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
