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.
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 necess
> --- classworlds.conf 3 May 2004 03:47:51 - 1.4
> +++ classworlds.conf 7 May 2004 18:01:42 - 1.5
> @@ -1,4 +1,6 @@
> -main is org.apache.maven.MavenCli from root
> +main is org.apache.maven.MavenCli from core
>
> -[root]
> +set maven.home using ${user.home}/maven.properties d
jvanzyl 2004/05/07 11:01:42
Modified:maven-core/src/bin classworlds.conf
Log:
o take advantage of a feature added to classworlds which allows the setting
of system properties with instructions in the classworlds.conf, this means
that m2 no longer requires the specification of
jvanzyl 2004/05/02 20:47:51
Modified:maven-core/src/bin classworlds.conf
Log:
o tools.jar isn't required, the compiler component should know how
to find what it needs and it does.
Revision ChangesPath
1.4 +0 -1 maven-components/maven-core/src/bin/classworld
