I thought I'd read somewhere that when compiling an aggregated group of projects (using the <modules> element in the aggregator project), Maven will use the target directories of the previously compiled projects when looking for dependencies. For example, say I have a project that aggregates projects A and B, where B depends on A. If neither of these artifacts exists in any repository, doing a mvn package is supposed to work despite the fact that project A isn't getting installed to the local repository--Maven will know to find it in project A's target directory. Anyway, I say I thought I'd read this, but now I can't find anything that says this. So I ask you: is Maven supposed to work this way? It currently doesn't, and I'm not sure if I should write a bug or not. ..David..
