Is there any way to configure Archiva to download missing Maven project modules if they aren't in the local workspace?

I'm confused about how Archiva fully works. I understand that if we had a core set of dependencies, we could use Archiva as our local maven repo.

The thing I don't understand, is how Archiva manages build artifacts from your own projects.

Say I have a multi-module maven project - we can even use the one from the Sonaytpe for example. http://www.sonatype.com/books/mvnex-book/reference/multimodule开发者_如何转开发-sect-building-multimodule.html

What if I wanted to have one team working on the Simple Model app, while I wanted another to work on the Simple webapp. But I didn't want either to have the projects they AREN'T assigned to, in their local workspace. Webapp needs Model to build, but I don't want the Wepapp team having direct access to Model.

Is there any way Maven can detect that the build artifact for Model wasn't in a Webapp dev's workspace, and pull it from our local Archiva repo, so they can still build the Webapp despite not having the model (maven module project) code in their workspace?

---

The Model project will be like any other third-party dependency and be downloaded by Archiva automatically, provided

• the Webapp project specifies Model project as a dependency
• the Model project is deployed to Archiva periodically (by a Continuous Integration system or other means).