On Fri, 30 May 2008 03:42:09 [EMAIL PROTECTED] wrote: > > So there seems to be 3 possible conclusions: > - There is any easy way to make these kinds of cascading releases, but we > just don't know about it > - There is a better way to structure our Maven projects so this doesn't > happen in the first place (keeping in mind that we are happy with how the > code itself is architected currently) > - This is just the way it is, so we should get used to it > > Can anyone comment on this? release early release often... we don't use snapshot dependencies and release artifacts early. So if you are working on one of the 13 dependent libraries as soon as you - the dev - is happy the change is ready for use then you release it. why leave it as a snapshot? If the change would break anything useing it we bump the major version up so its not pulled in until downstream users are ready.
if you use version ranges and manage codelines by major version then you can easily have the trunk of a project being actively developed and released without pulling it into a deliverable. -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
