For what its worth:
1) We do not use the Maven release plug-in and follow what Barrie
described below - SCM tags, etc.
2) We do not use profiles.
3) By getting the libraries out of our code, we make the wars very small
which might help more in this case where a lot of people are downloading
bug fixes over slow lines. We generally do not change the provided
libraries within a minor update so they are very stable and there is no
need to download 20Mb to get 20Kb of code that changed. Things like CXF
are huge and are used everywhere in our application so it makes a big
difference in the builds if you have to include it in every war file.
Ron
On 16/10/2012 5:56 AM, Barrie Treloar wrote:
On Tue, Oct 16, 2012 at 7:36 PM, Stephen Connolly
<[email protected]> wrote:
[del]
See what happens when your thread reaches critical mass!
Kittens die.
p.s. Thanks for an in-depth email that will be very useful for the archives.
The "Maven Way" for a release process isn't really well documented
anywhere yet, and I fear a few more kittens will die over that debate
as well.
Most people bump into release:process and blindly follow that path and
there a limitations with that option.
SCM commit/tags and mvn deploy are just as good.
Its really important to understand what is being automated before automating it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
