Mark, Mark McBride <[EMAIL PROTECTED]> wrote on 17/08/2003 02:11:52 AM:
> My group is currently running into the same problem.What we are doing is > declaring all our system/lib jars in a projects.xml which all our > projects extend. This is nice in respect to ensure that everyone is > building/debugging against the libraries that are in production. We are > actually using this parent project.xml to document our system > configuration. We declare dependencies on a per project basis and use the convergence report to stay in synch. > Another concept that we think would be a good feature of maven is the > ability to state a group of dependencies, say struts and all it's > libraries. This would be stated in a xml file that declares all the jars > that struts uses. This xml file could be stored in the maven central > repository so that projects that want to use struts 1.1 and all related > libraries could declare (maybe call it a "group dependency") this file > in it's project.xml and when doing builds maven would pull down the > struts dependency list and then check if those libraries have been > downloaded to the developers local repository.We tend to use frameworks > that consist of 5+ libraries which all depend on each other.Managing > dependencies through "groups" of libraries would ease setting up new > projects, and give more structure to dependencies. Transitive dependencies have been discussed and are planned to be implemented. All that's missing is a volunteer or time. > I'm not sure of how hard this would be to implement, whether it would be > to hack the project.xml or go directly into the maven impl??? I'd be > willing to work on this functionality if others (committers +) thought > this was a good idea/approach. The approach that's been discussed is for a project to list another project's 'pom' in it's dependencies and for the dependency verifier/ resolver to work out what they are at run time and add them in. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
