We use: * Build each Project fully. * NO circular dependencies (so a dependant project higher up the stack always has all confs below it created) * Use the non published ivy file to work out the build list (custom resolver only for CI/stack building)
I cannot see why you need to care about confs if you follow the above three rules. If you eliminate circular dependencies. Could you give an example where this fails for my understanding? Thanks, 2009/11/24 Jonathan Oulds <jonat...@sbdev.net>: > Dear all, > > I am using Ant+Ivy to specify the dependencies within a large software > project containing a mixture of C++ and Java code. I then use ivy:buildlist > to ensure that all targets are build in the correct order. > > However I have now run into a problem. Namely that the list of build.xml > files may be different for different configurations, however ivy:buildlist > does not seem to take account of configuration information within ivy files. > > Now I'm sure the the answer to this will be "simply resolve each project > before it is built, then the build order is irrelevant" however in this > particular case I need to build without access to the artefact repository. > > Am I out of luck in hoping that Ivy can help automate my build. Or has > anyone come across the same problem and arrived at an ingenious solution? > > Thanks in advance > Jonathan > > -- Alex Foreman
