Help with dependecies and release management

["Helck, Christopher" <ch...@ebs.com>]

Hi,

I'm looking for pointers about release management with Maven. The basic
question is how to handle certification builds for components? If I have
an application that uses 5 components and I modify one component (a bug
fix) how should I do a release? 
  I could modify the component and release it with a new version number.
  I could modify the component and application and release them with new
version numbers.
  I could modify all the components and applications and release them
with new version numbers.

Currently we do the third option because it was easy. Certification does
one large multiproject build. Soon we will have multiple applications
that share common components that have different release scehdules. The
big multiproject build will not work. Should we build components
seperately? The certification group will not want to build three or four
components seperately just to create a release of one application.

How do people handle these issues?

Thanks,
Christopher Helck


 
Thank you for being part of it.
 
The information contained in this e-mail is confidential. This e-mail is intended only for the stated addressee.  If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. if you have received this e-mail in error, please inform us immediately and delete it and all copies from your system.

EBS Dealing Resources International Limited. Registered address: 10 Paternoster Square, London EC4M 7DY, United Kingdom. Registered number 2669861.

EBS Dealing Resources, Inc, registered in Delaware. Address: 535 Madison Avenue, 24th Floor, New York, NY 10022, USA, and One upper Pond road, Building F - Floor 3, Parsippany, NJ 07054, USA.

EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku,  Tokyo 104-0033, Japan.