Hi I wonder if another way of doing this is to allow one project to have a depenedency on another maven project, instead of just on individual jars, a transitive property for projects. That would address the need of a common depend list, as you could just make an empty project that contained the common dependencies, but no actual code.
This would also allow maven to "find" dependencies of dependencies. For example, if my project AAA has a dependency on another maven project BBB, which depends on c.jar and d.jar, then I only have to have <dependency> <projectid>BBB</projectid> <version>SNAPSHOT</version> </dependency> in my project.xml, and the c.jar and d.jar will be included in my dependency list. Also, if project B decides to add b3.jar to the next SNAPSHOT, then my project automatically gets notified and b3.jar is downloaded the next time I run maven. I guess the catch is that there would have to be a dependency-1.0.xml in the repository as well as the jar so that this info could be automatically recovered. Alternatively, I suppose the entire project.xml file could be put there, but that might be too much. Probably there would have to be a check for circular dependences as well. just a thought, Philip -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
