Eric Brown wrote:
My project is using maven2 and the release plugin. However, the release
plugin only works with released plugins (otherwise, our release builds
are not reproducible). We've had to locally patch a half-dozen plugins
just to mark them as released just in order to be able to do a release
build of our project. Furthermore, there are many core and non-core
plugins that have plenty of bugs fixed that we still experience today in
their SNAPSHOTs. But we can't use these.
There is no shortage of numbers in the world. What is the problem with
releasing often? So what if a bug occasionally gets its way into a
release -- you can always specify an older version of a plugin that
didn't have some new bug.
True, a lot of plugins are under 3rd party control and not part of the
core maven. But if the core maven team starts releasing more often and
understands why releases are important, many of the 3rd parties will
follow suit.
Right now maven seems more like a toy and is constantly frustrating when
trying to use it on a real project (due largely to known bugs many of
which have been fixed in SNAPSHOTs for over 6-months now and/or several
plugins that have produced SNAPSHOT builds but no released version).
BTW, My project releases weekly. So far we have 0.5-rc1, 0.5-rc2,
0.5-rc3, ... 0.5-rc9. And we have SNAPSHOTs in between that we never
deploy to production but which developers work with.
Cheers,
Eric
Hi Eric,
During the last couple of months a lot of work has gone into releasing
new versions of the plugins that are used during the release process.
When all these plugins have been released, less time and effort will be
needed to release something. So then we will be able to do more frequent
releases of plugins.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
