We stayed manual. I figured it was a small overhead at the start of a
new release cycle but we only had 70 modules to manage and we were
pretty modular.
I suppose Ant and XLST scripts would do the job pretty well.
Check out each project.
Use XSLT (or some other XML transformer) to fix the right dependency
Maven to build
Check-in the project.
Ron
On 18/06/2012 9:19 PM, James Carman wrote:
We are an OSGi shop. Thus, we have a lot of "bundle" projects that
have their own independent release cycles. We have a hierarchy of
parent POMs and many utility libraries. When we change one of the
upper-level POMs (like the "base" for all of our OSGi bundles), it is
very time-consuming to point all of the downstream projects at the new
version. How do folks typically handle this? There has to be an
easier way. I found the versions plugin [1], but that can only get
you so far. You still have to cut each of the releases and re-point
everyone at them. Yuck!
[1] http://mojo.codehaus.org/versions-maven-plugin/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
