On Fri, Nov 5, 2010 at 1:57 PM, Phillip Hellewell <[email protected]> wrote:
> On Fri, Nov 5, 2010 at 12:16 PM, Stephen Connolly > <[email protected]> wrote: > > > > This could be a bad thing. > > > > If A actually needs C to compile, then keep the dependency on C as the > > transitive deps pulling in C could change and no longer pull in C. > > In many of my cases, yes A actually does need C to compile. > In that case - my suggestion wont work for you. Also - after re-reading this thread it seems your assuming something very simmilar to what I assumed when starting with maven: namely ive I have changed B while working on A, and I build from within project A, maven will also pickup the changes from B -- this is not true. What will actually happen is A will be compiled based on the last installed version of B. IMO the better option is to Always build from the top level of your project, then changes across modules are always built together with dependencies in the right order.
