so tell management to keep out of the code and give them there 6 discreet version numbers that are the official deliverables... how you put those deliverables together should be technical decision that gives the most robust repeatable result possible.
we've got 113+ artifacts in 15 groups with 7 deliverables (plus the other 170 third party artifacts that get pulled in... ) each artifact has its own lifecycle. The last project i worked on went from a similar setup for 5 or so version numbers... with snapshots... it made life incredibly painfull for them.. On Wed, 12 Dec 2007 08:46:50 Graham Leggett wrote: > Michael McCallum wrote: > > what is the benefit in having one version? > > Sometimes code needs to be separated into different jars or EJBs for > operational reasons, where it makes no sense to release separately. > > In other cases, code can be in a state of transition, where code is > first refactored into a separate jar, which is then spun out to have a > lifecycle of its own. > > There is no "one size fits all" strategy for all projects, especially as > projects evolve over time. > > (We have 5 primary projects, with 5 discrete version numbers, and we are > negotiating to arrange a sixth. Politics takes time.) > > Regards, > Graham > -- -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
