Will this problem addressed in 1.1 or 2.0?

-Dan



On Fri, 3 Dec 2004 10:25:01 +1100, Brett Porter <[EMAIL PROTECTED]> wrote:
> Yes, that will still be a problem as we haven't introduced the
> temporary file handling/locking.
> 
> - Brett
> 
> 
> 
> 
> On Thu, 2 Dec 2004 15:05:10 -0800, dan tran <[EMAIL PROTECTED]> wrote:
> > Thanks Brett
> >
> > What bout the case where I have share $HOME and paralle builds on
> > multiple hosts happen to download the same artifacts?  That would be
> > collision. isn't it?
> > What is the best approach?
> >
> > Many thanks again.
> >
> > -Dan
> >
> >
> >
> >
> > On Fri, 3 Dec 2004 08:57:17 +1100, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > >   1.  Since I have no access to other directory except $HOME, therefore
> > > >        I need to install it some where in $HOME, what happens if have
> > > >        multiple maven builds in paralelle on mulitple host sharing the 
> > > > same
> > > >        maven installation?
> > >
> > > It should work just fine.
> > >
> > > The only thing to watch out for is that you don't install new plugins
> > > using plugin:install/download while a build is running as it will
> > > delete files from ~/.maven/cache that might be in use.
> > >
> > > >
> > > >   2.  Can I make maven install shared for every one on same host?
> > > >        I doubt that it is possible since maven need to modify
> > > >        $MAVEN_HOME/plugins dir
> > > >
> > >
> > > You don't have to be able to write to the plugins directory. Users can
> > > put their new plugins in their own ~/.maven/plugins.
> > >
> > > The only problem is that at present plugin:install and plugin:download
> > > don't have semantics to do this for you.
> > >
> > > - Brett
> > >
> > 
> > ---------------------------------------------------------------------
> > 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]

Reply via email to