> > Another desire I have is to allow for developers not even building > most > > of the modules, and just letting the "ear" project pull snapshot > > artifacts from the Nexus repo (built by the release team or > continuous > > integration). I could do this with multiple "build" projects, > including > > different sets of "module" elements. That seems messy, however.
You don't need separate projects for this. You just need a bunch of developer-facing pom files with different <modules> lists. They can certainly live in the same directory. This is something we definitely take advantage of, for producing interesting developer build sets. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
