On Fri, August 12, 2011 10:34 am, leonfranzen wrote: > My organization has been using Maven and CI for a few years now. Although > we > have a process in place that works for us, it has always been difficult to > come up with a successful approach to dependency version management in > Maven > at release-time. We use the release plugin extensively, are familiar with > the version plugin and use them both in an attempt to automate the process > as much as possible but I feel that our approach may not be a > "best-practice". The Sonatype CI best practices blog post was very > helpful > but I think it was light on details regarding dependency version handling. > The two areas I feel we have the clunkiest processes are: > 1. When a component is released, we don't have a good way to automatically > update dependent projects that need a corresponding snapshot version > reference update. What is the recommended Maven best practice for > synchronizing snapshot dependencies in a complex dependency tree? For us > this requires an awareness of the dependencies and manual notification and > maintenance.
What about using dependency management in a parent pom? > 2. Just prior to release time, we have snapshot dependencies. What is the > recommended Maven best practice for transitioning those references to > released versions while still maintaining proper continuous integration of > trunk source changes to the dependencies? In other words where does CI go > when we fix our dependency references around release time? We want to > avoid > any concept of code-freeze around these times. Depending on your scm strategy e.g. trunk moves straight to the next snapshot, release branch gets separate CI setup.. Of course depending on your CI server and SCM things around this idea might vary.. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
