That's the right aproach when all submodules are build together (which seems to be the case here because there is a single revision number).
However, if you have lot of submodules with complex inter-dependencies, it might be difficult to setup and maintain everything in a single ivy file. The other alternative is to use one ivy.xml per submodules. Nothing prevent you to release all those submodules together with the same revision number. And concerning the pattern that you want to use : organization/product/revision/submodule. You should try to setup the m2compatible flag to true (See [1]), and put "XXX.PPP" in the org field of your dependency declaration in the ivy files. [1] http://incubator.apache.org/ivy/doc/resolver/filesystem.html Gilles 2007/6/24, John Gill <[EMAIL PROTECTED]>:
Use configurations to identify the different "sub-modules", and then when the other projects resolve and only want one of the sub-modules, they specify the configuation they want to use. On 6/24/07, Scott Goldstein <[EMAIL PROTECTED]> wrote: > > I have a use case in which a product contains a number > of submodules which can be used individually. So, in > essence, the submodules are identified by: > > organization/product/revision/submodule > > It doesn't appear that Ivy has such a notion in its > depedency resolution mechanism. Am I correct? > > I could replace one of these tokens with the "branch" > element, but I don't think that this was the intended > purpose. > > I suppose another approach, here, would be to write a > custom DependencyResolver in which for the module, I > would specify something like "product:submodule" and > my resolver would split these up and apply them to a > pattern. > > Are there any other approaches that would make more > sense? > > Thanks. > > Scott > -- Regards, John Gill
