Thanks, just wanted to be sure. -Dave
On Tue, Sep 22, 2009 at 11:51 PM, Anders Hammar <[email protected]> wrote: > A project having (child) modules is a different story than a project having > dependencies. Modules are not dependencies. So, you declaring a dependencu > on an aggregating project (a project with modules) will not add the modules > as transitive dependencies. > If you have dependencies on any of the modules in question, you should > declare a dependency to that artifact in your project. > > /Anders > > On Tue, Sep 22, 2009 at 22:12, David Hoffer <[email protected]> wrote: > > > I notice that specifying a pom type dependency on a pom that has child > > modules (e.g. it's a pom type) does not include those dependencies nor > > their > > transitive dependencies. However a pom type dependency on a pom that is > > not > > of pom type itself does bring in that dependency and its transitive > > dependencies. > > > > Is this expected behavior? Is it configurable? > > > > -Dave > > >
