You could do the following... Copy ~/.m2/settings.xml to ~/.m2/settingsy.xml Configure localRepository in settingsy.xml to point "somewhere else"
Copy MAVEN_HOME/bin/mvn.bat to mvny.bat Edit mvny.bat and append "-f ~/.m2/settingsy.xml" to the call to mvn Then call normal "mvn" from X, and mvny from Y. This will automatically use the 2 localRepositories without messing with poms or logging in as 2 users etc. You just have to remember to use mvn in one window and mvny in the other. Wayne On 3/19/08, Dan Fabulich <[EMAIL PROTECTED]> wrote: > Brian E. Fox wrote: > > >> Samuel Le Berrigaud wrote: > >> > >>> 1. only run mvn verify, this way nothing gets installed into the local > >>> repository, > >> > >> This doesn't work in a multi-module reactor build where the modules > >> depend on each other, does it? > > > No, it will only work if you at least do compile (then a reference to > > /target/classes is passed instead of the jar) > > Huh? verify is after compile, right before install. (Actually, I did > "package", then later tried "verify" to see if it would work; neither > did.) Should that have worked? > > -Dan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
