On Mon, Feb 28, 2011 at 9:49 AM, Phillip Hellewell <[email protected]> wrote: > The problem I see with using a snapshot for the parent is it doesn't > allow you to make changes in a safe way. I could update the version # > of a lower component, and then a much higher component could build > against that before all the middle components are built/deployed. > This may not be a problem for Java or C#, but for C/C++ with headers > and static libraries, it is a recipe for disaster. We're talking > about things like inexplicable run-time crashes.
Actually, I just remember that with my version clash plugin in place, it will prevent this dangerous scenario. Instead, the higher components will get an error and not be able to build at all until the lower components have been built/deployed. So to prevent breaking all the builds right away, I need to update components to the latest parent from the bottom up, deploying as I go. In other words, I would end up doing pretty much the exact same thing I do now without using the parent for dependency management. Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
