An: users@maven.apache.org
Betreff: Re: Independent module release strategies
Our project was about 50% larger in terms of modules and we did what you
are suggesting and got rid of the idea of increasing versions on
artifacts that did not change.
I am not sure why this is causing you more
Von: Wayne Fay [wayne...@gmail.com]
Gesendet: Dienstag, 16. Oktober 2012 01:26
An: Maven Users List
Betreff: Re: Independent module release strategies
The project consists of about 50 Maven artifacts. A lot of people are
using this project all over
@maven.apache.org
Betreff: Re: Independent module release strategies
Our project was about 50% larger in terms of modules and we did what you
are suggesting and got rid of the idea of increasing versions on
artifacts that did not change.
I am not sure why this is causing you more problems
On Tue, Oct 16, 2012 at 7:36 PM, Stephen Connolly
stephen.alan.conno...@gmail.com 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
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
Hi,
I am currently working on finetuning the workflows on a large application that
was migrated from an Ant based build to one based upon Maven.
The build itself is running smoothly but, what I'm currently working on is
getting the release workflow optimized.
The project consists of about 50
Our project was about 50% larger in terms of modules and we did what you
are suggesting and got rid of the idea of increasing versions on
artifacts that did not change.
I am not sure why this is causing you more problems rather than less.
We had a master spreadsheet listing all of our modules
The project consists of about 50 Maven artifacts. A lot of people are
using this project all over the world. The client is distributed by some
web-start similar solution.
The problem is whenever a bugfix-release is done, we don’t want to release
all modules in a new version because then all
On Tue, Oct 16, 2012 at 9:56 AM, Wayne Fay wayne...@gmail.com wrote:
I would expect that suggested approaches for solving your problem
may depend a bit on the answers to these questions.
Which come about because your software has a development lifecycle:
Developing Released Maintained End of
On 15/10/2012 7:39 PM, Barrie Treloar wrote:
On Tue, Oct 16, 2012 at 9:56 AM, Wayne Fay wayne...@gmail.com wrote:
I would expect that suggested approaches for solving your problem
may depend a bit on the answers to these questions.
Which come about because your software has a development
10 matches
Mail list logo
