> -----Original Message-----
> From: bob mcwhirter [mailto:[EMAIL PROTECTED]]
> Sent: 06 July 2002 15:15
> To: Turbine Maven Developers List
> Subject: Re: maven jars question
>
> > I'm not sure I am following the story with maven external jars and
> > lib.repo.
> >
> > When I built Maven from CVS I ran "ant -f build-bootstrap.xml". I
also
> > had a build.properties in jakarta-turbine-maven directory which
> > contained :
> >
> > maven.home = c:\apps\maven
> > lib.repo = c:\apps\repo
> >
> > I had also set MAVEN_HOME env variable to point to c:\apps\maven
> >
> > The results :
> >
> > * maven external jars were copied to c:\apps\repo
> > * they were also copied to c:\apps\maven\lib
>
> Yah, those are right.
>
> > * they were also copied to user.home\maven.repo !
>
> Really? At what point during the bootstrap did that happen?
bootstrap:
[copy] Copying 1 file to C:\apps\maven\lib
[exec] maven: intelligent projects
[exec] project-directory: E:\Dev\jakarta-turbine-maven
[exec] project: Maven (maven)
[exec] current-version: 1.0-b5-dev
[exec] [ERROR] Directory 'C:\Documents and Settings\Vincent
Massol\maven.repo' does not exist.
[exec] [ERROR] Attempting to create.
[exec] Getting:
http://jakarta.apache.org/turbine/jars/non-distributable-jars.list
[exec] Writing C:\Documents and Settings\Vincent
Massol\maven.repo\non-distributable-jars.list
[exec] .
[...]
>
> > 1/ Why do I have to specify in 2 different ways maven home : once in
> > build.properties and once in MAVEN_HOME. Can't we have only a single
> > property ?
>
> On unix at least, MAVEN_HOME is sufficient, and will be devined if
> unset. We ignore ${maven.home} as set through any properties files
> at this point, I do believe. (Because we need to know MAVEN_HOME
> when we start the process, we can't wait to read some props files)
If you look at build-bootstrap.xml you'll see it uses Ant lib.repo and
maven.home properties, not MAVEN_HOME. That's true for both unix and
windows, isn't it ?
MAVEN_HOME is used only after the bootstrap when maven.bat is used.
>
> > 2/ How can I tell Maven ng that my lib.repo is c:\apps\repo and not
> > user.home\maven.repo ?
>
> Yah, that's a little wacky.
>
> > 3/ Why do the maven external jars get copied both in lib.repo and
> > maven.home/lib ? Couldn't we have them *only* in maven.home/lib ?
>
> Nope.
>
> We want to allow folks to blow away ${maven.repo.local} to do fresh
> builds, but without kill maven itself.
I don't understand. If Maven relies on jars found in maven.home/lib,
then you can blow away maven.repo.local with no problem. It will not
kill Maven.
>
> Think of maven.home/lib as a deployment directory, containing all
> the dependencies of maven that it needs when deployed.
Exactly! So why do we need the same jars also copied into
maven.repo.local ?
>
> It's not a directory of jars to compile gainst, and
${maven.repo.local}
> isn't a directory of jars to deploy against. Each has its purpose.
What do you call a deployment directory ? What's its purpose ? Why do we
need one ?
Thanks Bob!
-Vincent
>
> -bob
>
>
> --
> To unsubscribe, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
