That's the safest option, but I also do this: m2 install && cp target/*.jar $M2_HOME/lib
for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > you need to run m2-bootstrap.sh > > Emmanuel > > Ashley Williams wrote: > > First of all what's the quickest way to update my maven installation? > > I'm very keen to avoid running the tests so I was hoping to do > > something like svn update, followed by m2 clean:clean install at the > > maven-components level. This would update my repository artifacts, but > > obviously I wouldn't get a new maven/bin directory. Is this direction > > workable? > > > > --------------------------------------------------------------------- > > 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] > >
