[Anthill] Versioned Dependency

Thompson, Andrew M. DOC Andrew.Thompson at doc.state.wi.us
Thu Jul 15 14:18:04 CDT 2004


Are there any plans to allow versioned builds for each member of a
dependency project?  The versioned build feature only automates the top most
level of what we had to do somewhat manually in the end any way.

Say we had three projects in a dependency group.  The "middle" one that is
both dependent and a dependency of the top level project has changed
(ProjectB), but a new version of the top most project is required
(ProjectA).  We want to build a new version of the top most project with
specific version of the dependency.  How we had to do this was first to move
a copy of the bottom most project (ProjectC) into ProjectB's classpath, this
is normally done for us using the dependency.artifact.dir and the
Depenedency groups, but to do a Versioned, we have to run the build directly
from ProjectB.  Once that is done, both jars from ProjectsB&C are moved to
the dependency.artifact.dir for the entire group. Then a manual (unforced)
build is performed on ProjectA.  

Is there a better way?

Thoughts?



More information about the Anthill mailing list