> > > * 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.
It's using the value of ${maven.repo.local}. How is yours set,
if at all?
> > 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 ?
Yes, but bootstrapping which only uses ant.
> MAVEN_HOME is used only after the bootstrap when maven.bat is used.
Yah... Though, maven[.bat] is used as the last action of bootstrapping,
so I reckon you do have to have them all set.. That is a bother. We
can probably find a better way.
> > 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.
Right, which is why we keep maven.repo.local and maven.home/lib separate.
Are we in disagreement?
> > 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 ?
So that you don't necessarily have to download them again when you
compile jakarta-commons-toejam, which might need some of them.
> What do you call a deployment directory ? What's its purpose ? Why do we
> need one ?
Just a handy place that's not going to be affected by further downloads
of possibly bogus jars. How much pain would you be in if someone put a
wacky commons-jelly.jar into the /turbine/jars/ that trampled the jelly.jar
that maven itself needs? Suddenly, you'd be dead in the water, unable
to build anything.
Also, in the event of a multi-user system, maven itself could be install
at /usr/local/maven/ or somewhere not world-writable. Each person could
still maintain their own maven.repo.local.
-bob
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
