amit kumar wrote:
Hi,
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.
Use version ranges. Developers can update versions in their modules and
other developers can pick up the latest version automatically by
declaring <version>[1,)</version>. As others have recommended, "Better
builds with Maven" is an excellent book about this and other topics.
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),
Again, version ranges help. You developers may update the lower boundary
for the version range from time to time just to make sure that the
features they need in their modules are present in the modules they
depend on.
You should also use the release feature of continuum or the maven
release plugin to make sure that the module versions are updated and the
jars are being properly deployed to the repository.
--
best regards,
Stefan Seidel
software developer
________________________
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel. +49 (341) 9 60 50 07
fax. +49 (341) 9 60 50 92
mail. [EMAIL PROTECTED]
web. www.vub.de
HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
