internal dependencies check, excluding local repo

[Valerio Schiavoni <va...@gmail.com>]

hello everyone,
given a multi-module project, does it make sense to resolve the dependency
to a given module without checking if a new version of it has already been
installed to our local repository ?

That is, given this :

parent/
          sub-1/
          sub-2/

sub-2 must always be aligned with developments being made in sub-1: that is,
i can't be sure that developers on module sub-1 always perform a deploy over
our internal repository, but still i'd like maven to see if the current
local copy is up-to-date to the one on our scm: if not, update my local
copy, compile those just-checked out sources, install them, and just after
all this build sub-2.

Does any one has this need?

thanks,
valerio

-- 
http://valerioschiavoni.blogspot.com
http://jroller.com/page/vschiavoni