Is there a way to indicate dependencies between sibling modules using just build artifacts (e.g. not requiring an install into local m2 repository nor push to a remote one)?
Every time I indicate a dependency between sibling modules, maven seems to look to satisfy the dependency elsewhere than the project's build environment. I suspect my issue is that I'm not thinking lifecycle-y enough, but still viewing the world through ant-ish glasses. (Yes, this is related to my earlier question about needing to get classes in path for hbm2ddl; it actually works fine for the dependencies *between* the two multimodule projects; it's satisfying the dependencies within one multimodule project that I'm still having trouble completing.) Thanks, dwh
