Your aggregator POM should include all the transitive dependencies unless you excluded them since you are providing them elsewhere (using another POM). The person needs to include a dependency on the aggregated POM and the "elsewhere" POM
On 10/01/2011 12:16 PM, Leon Rosenberg wrote:
Hi, so I have 4 projects with one aggregator pom and it works just fine for publishing and releasing. I have an aggregator pom, which includes a,b,c,d and it all got built and stuff. Now, if a user of mine wants to use this project, he has to know which of the a,b,c,d modules he actually need, or which is the one, that includes the other. I thought I could save the user the searching and let him just declare the dependency to the aggregator pom, but it obviously don't work (cause maven tries to download the aggregator.jar and not the transitive dependencies). Now for the question, what is the best practice here? Is defining a module with a sounding name, like the-module-you-have-to-include-in-yourpom which is simply a pom, defining dependencies to a,b,c,d and which can be used for transitive resolution, the way to go, or is there another practice? thanks in advance Leon --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
