The "dance" was only required because we have a hierarchy of poms and one of the top-level guys had to change. This change was required to make the OSGi stuff "happy", so it had to be propagated down.
I ended up writing a simple ruby script that searches through all of the pom.xml files in a directory and cuts all of the "-SNAPSHOT" suffixes from any parent or dependency references. Then, I went into Jenkins and did the releases from the "top" down. On Mon, Jun 18, 2012 at 11:56 PM, Barrie Treloar <[email protected]> wrote: > I think what Ron is saying, is that choosing what Project A depends on > is selected at the time Project A is kicked off. > Until Project A is released all its dependencies should be locked down > and only use release versions (if possible). > You would only upgrade a dependency when a critical bug blocks development. > Rather than doing this "dance" every time every project releases. > > That way you only have one point in your development process (i.e. > start of a new sprint) that you have to worry about doing all this > work. > And it should be relatively easy to do, maybe > http://mojo.codehaus.org/versions-maven-plugin/use-latest-releases-mojo.html > > This does mean your CI environment may not be testing the latest > versions of the dependency chain. > If you want that you may create a "shell" project that just has > .snapshot qualifiers. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
