> 1) During the development process within an iteration, how to make > sure that all the module owners dependent on "a.jar" keeps up to date > with the changing versions of a.jar as the development goes on until > Integration Testing. It sounds to me like you want to use a SNAPSHOT version within each iteration. That way dependent module owners don't need to constantly update their poms. Once you hit your testing phase, do an "alpha" or "beta" release of all the modules and test against that. Just my 2 cents. Justin
________________________________ From: amit kumar [mailto:[EMAIL PROTECTED] Sent: Wed 2/6/2008 9:25 AM To: users@maven.apache.org Subject: Conceptual Confusion about build and release process using maven. Hi, Please pardon me for such a long mail but couldn't cut it any shorter. After 2 months of being assigned the task of mavenizing the whole product at my workplace and build and release automation process with Continuous Integration, I have been able to mavenize the product and put continuum and mavenized CVS structure in sync. But while pondering over how to go about with the build an release strategy I got myself in deep confusion. The product (as usual) has several submodules with separate developers and with many intermodule dependencies. My understanding of the whole process till now has been like below Development environment, after intranet maven repository in place would be something like this: owner of module A would deploy the A.jar on maven repository from where the other module owners which depend on a.jar would fetch it from. And as the development goes on for module A, the owner of module will keep on changing the versions (with in an iteration as well) and deploying it on to the maven repository and dependent modules will keep on changing the version in their pom.xml for "a.jar".(unsure about whether this is how it happens) All these developments in various modules keep on getting committed into the CVS from where the Continuum keeps on checking out and building ( Continuous Integration). Now my confusion over my own understanding and assumption is: 1) During the development process within an iteration, how to make sure that all the module owners dependent on "a.jar" keeps up to date with the changing versions of a.jar as the development goes on until Integration Testing. 2) If a module owner dependent on a.jar fails to update the version of the a.jar in the pom.xml and/or miss to commit the updated pom.xml with a contemporary version of a.jar. Continuous Integration at Continuum would suffer( assuming that even with not up to date version of a.jar the module still gets through build), Pardon me for any wrong assumptions, I do not have much exposure to the process. Regards, Amit --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
