For 2, this can be achieved by adding the group of dependencies to a project of type pom and then including this group project as a dependency whenever you need to include the whole group of dependencies. You mark the dependency as of type pom and it just pulls in all the transitive dependencies.
2009/8/18 Tako Schotanus <[email protected]> > Yes, that is an option but one that will only work if ALL subprojects > need those dependencies, something that isn't the case in our > situation. And we don't want to subdivide our hierarchy even more just > to to be able to define dependencies. Ah well, that's just the way it > is then :) > > -Tako > > > > On Tue, Aug 18, 2009 at 10:26, Anders Hammar<[email protected]> wrote: > > 2) I believe inclusion like this is planned for Maven 3.0, but for M2 you > > have to settle with using a parent where you define common dependencies. > > > > /Anders > > > > On Tue, Aug 18, 2009 at 09:43, Tako Schotanus <[email protected]> wrote: > > > >> Hi, > >> I've got 2 questions that I haven't been able to find an answer to: > >> > >> 1. For maven projects of type WAR is there a way to still have it > include > >> the contents of WEB-INF/lib in the class path during > compilation/packaging? > >> For a project we're doing we have a large list of 3rd party JARs that we > >> need to include and I don't want to set up a central repository and add > >> them > >> there or have every developer add them to their local repository. > >> > >> 2. If you have several projects which all share a certain largish set of > >> dependencies, is it possible to define those dependencies somewhere and > >> "include" them? > >> > >> Cheers, > >> -Tako > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
