On 2009-12-10, sebb <seb...@gmail.com> wrote: > As the subject says - do GUMP M2 builds really need dependencies to be > specified?
It depends. > Surely the M2 POM provides all the information required? It does. <option> and <depends> in Gump descriptors fill more than one purpose, though. One is building up CLASSPATHs for Ant builds and jar overrides for Maven 1 projects, this is not necessary in the mvn case. The other one is determining build order and this remains important in the mvn case as well. If a mvn built project A uses project B it will query the Gump mvn proxy for it and if B has been built before A it will get the Gump built version. Everything is fine. If B gets built after A, A will get a static version of B from the central repository - and even worse, it will put that version into the local repository so that the Gump built version won't even get used once it becomes available. So <option> and or <depends> is still useful. I usually stick with <option> so build order is deterministic but the project gets built (against the released version of dependencies) even if the dependencies fail to build themselves. Stefan
