You could solve your "first run of Maven every day is slow" issue by creating a cron job to run "mvn depedency:go-offline" on your project(s) at 6am every day.
Right now, having multiple threads of Maven running at the same time using the same local repo cache is a bad idea. A few new implementations have been discussed on dev@ and I imagine we'll see some changes there at some point. Wayne On 12/20/07, Johannes Schneider <[EMAIL PROTECTED]> wrote: > Some points are really problematic with Maven. Every day the first usage > of maven on each project is really slow. I would like some sort of > improvement with this. > > What about adding the possibility to download commonly used plugins > after installation (just a script...). > > What about preparing some scripts (that can be used as cronjob or at > boot time) that resolve some dependencies in the background? > Adding some intelligence should be possible. > > What about using several threads to look for library updates? > What about setting shorter timeouts (ever tried to use maven if a > repository is not available?) > > > This are small improvements that don't change the internals or > principles of maven but could improve my user experience a lot. > > > Regards, > > Johannes Schneider > > Borut Bolčina wrote: > > Anybody saw this post? > > > > http://fishbowl.pastiche.org/ > > > > Unfortunately the author, Charles Miller <[EMAIL PROTECTED]>, disabled > > the comments to prevent spam. Hmmm. > > > > Regards, > > Borut > > >
