Jason van Zyl <[EMAIL PROTECTED]> wrote on 09/05/2004 11:45:38 PM:
> On Sun, 2004-05-09 at 04:40, Emmanuel Venisse wrote:
>
> > Personnaly, I prefer an env var definition. Is it possible to use this
> > process :
> > 1- check if ${user.home}/maven.properties exists
> > 2- if not, check if ${user.home}/m2 exists
> > 3- if not use $M2_HOME env var
> >
> > And, the M2_HOME is necessary for the bootstrap process.
>
> This can be fixed, but why make the user specify an envar if they don't
> have to? In addition for the embedded mode of use you don't want any
> platform dependendent mechanisms being required. I think requiring an
> envar something that should be avoided if possible.
You're going to need the ability to have multiple Maven's installed
eventually, like we can for M1.
It doesn't look like the properties file route will handle that as well as
an environment variable.
--
dIon Gillard, Multitask Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
