I saw at one place where versions of all the projects are defined in a pom and made this pom parent pom to rest all the poms. Placeholders are used in all the children poms. This provides flexibility to change the version of only the changing components.
This is not recommended for a project having large number of modules. What is the group's stake on this? On Thu, May 24, 2012 at 6:03 PM, Thiessen, Todd (Todd) <tthies...@avaya.com>wrote: > That is where test automation comes in. Steve had mentioned Selenium. It > works quite well but there are false negatives now and again. We are at a > point now, however, where these are few and far between. But to do so we > have kind of had to write our own wrapper around Selenium to get around > some of Selenium's shortcomings. > > My 10 minute rule is just one guide line. Steve pointed out another (ie: > break out modules that are harder to build reliable tests for) and Ron I > view yours as very important as well (ie: logical separation of components > to allow for increased parallel development). All great points which I > would recommend the original poster take into account when devising his/her > own versioning strategy. > > > -----Original Message----- > > From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > > Sent: Thursday, May 24, 2012 11:38 AM > > To: users@maven.apache.org > > Subject: Re: Maven versioning > > > > We just got tired of checking out modules, updating the versions, > > building and testing them, deploying them into production all just > > because some other module had a bug in it that needed fixing or > > required > > an enhancement. > > > > We have not yet figured out how to test UI in an automated way. > > > > We broke things up into functional modules so people could work on them > > in parallel. > > We went to SOA so we could write robust code. > > > > The proliferation of modules was not generally caused by the build > > taking too long. > > > > I am not sure that we are smart enough to write anything that takes 10 > > minutes to build with a high level of confidence that it is bug free. > > Nothing that we have takes more than 1 minute to build. > > > > Ron > > > > > > On 24/05/2012 11:00 AM, Thiessen, Todd (Todd) wrote: > > > I am on the same page as Ron here. But I know you will get a > > different answer for different maven users. Just recently, someone was > > asking a similar question on this list and he/she very much wanted one > > large checkout where all modules have the same version and was against > > breaking it up into individually versioned parts. > > > > > > It is a bit of an art to decide when a multi-module project becomes > > too large. My rule of thumb is the 10 minute build. If building > > everything takes longer than 10 minutes, it is time to think about > > breaking it up. > > > > > >> -----Original Message----- > > >> From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > > >> Sent: Thursday, May 24, 2012 10:44 AM > > >> To: users@maven.apache.org > > >> Subject: Re: Maven versioning > > >> > > >> We started out with a "Yes". > > >> As the number of modules grew to over 70 and the reasons for new > > >> releases got more functionally oriented, we went to "No". > > >> > > >> Philosophically, we looked at our use of Apache libraries (and other > > >> third party libraries) and reasoned since we were very comfortable > > >> using > > >> third party libraries with version numbers that were different than > > our > > >> release, why should we be hung up on changing the version on > > something > > >> that did not change. > > >> > > >> We also moved to SOA as a major architectural foundation so changes > > to > > >> the database and the API for the basic objects started to have less > > >> impact on the presentation and business layer since the services > > >> isolated the impact of low level changes to only those modules that > > >> need > > >> to deal with the updated data elements. > > >> > > >> We went high-tech to manage the versions. > > >> A spreadsheet listing the modules down the rows and the version of > > the > > >> module that is used in each of the releases in the column for each > > >> release.;-) > > >> > > >> We have a team planning session at the start of each release to > > >> identify > > >> which modules will change. > > >> The definite need to look at each module in this initial stage as a > > >> team, also helps understand estimates and timelines a bit better. > > >> > > >> We are mostly right at the start but sometimes we get a surprise > > during > > >> development and have to update the spreadsheet. > > >> > > >> Saves hours of useless work and sometimes makes debugging a bit > > easier > > >> since you have a clearer idea about what module changed, when and > > why > > >> just by looking at the spreadsheet. > > >> > > >> Downside: A bit messy looking in deployment. > > >> > > >> We use Subversion and Eclipse STS so branching and tagging is > > >> available. > > >> > > >> Ron > > >> > > >> On 24/05/2012 8:39 AM, DK wrote: > > >>> Hi, > > >>> > > >>> New to Maven and have a couple of questions around versioning. > > >>> > > >>> Should all projects within a multi-module project have the same > > >> version? > > >>> Should all projects related to each other keep the same version > > >> number? > > >>> Any best practices on changing version numbers? > > >>> > > >>> Thanks > > >>> > > >>> -- > > >>> View this message in context: > > http://maven.40175.n5.nabble.com/Maven- > > >> versioning-tp5709659.html > > >>> Sent from the Maven - Users mailing list archive at Nabble.com. > > >>> > > >>> ------------------------------------------------------------------- > > -- > > >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > >>> For additional commands, e-mail: users-h...@maven.apache.org > > >>> > > >>> > > >> > > >> -- > > >> Ron Wheeler President Artifact Software Inc email: > > >> rwhee...@artifact-software.com skype: ronaldmwheeler phone: > > >> 866-970-2435, ext 102 > > >> > > >> -------------------------------------------------------------------- > > - > > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > >> For additional commands, e-mail: users-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > -- > > Ron Wheeler President Artifact Software Inc email: > > rwhee...@artifact-software.com skype: ronaldmwheeler phone: > > 866-970-2435, ext 102 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
