> -----Original Message-----
> From: bob mcwhirter [mailto:[EMAIL PROTECTED]]
> Sent: 06 July 2002 15:38
> To: Turbine Maven Developers List
> Subject: RE: maven jars question
>
> > > > * 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?
Haha ... No I haven't set that property anywhere. Actually I don't know
how to do that with maven ng. As I said, I have a build.properties in
which I define maven.home and lib.repo. That file is used by
build-bootstrap.xml. Is it also used by Maven ng ? In which case, does
it mean I need to define maven.repo.local in it, in addition to lib.repo
(both pointing to the same location) ? Or is it done in another way in
Maven ng ?
>
> > > 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.
That was my point ... :-)
>
> > > 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?
Yes ... almost. If I understand what you are saying, Maven ng uses the
jars in maven.home/lib *over* the ones in maven.repo.local, which means
I can actually remove the jars in maven.repo.local with no problem and
Maven ng will not copy them again there as it will find them in
maven.home/lib ?
Let me explain why I don't want the Maven jars in lib.repo.local. I have
a project that I want to build with Maven. This project depends on
external jars that I check in CVS so that all our teams can get them
easily and in their correct versions. For us, our maven.repo.local is
the location where we put our *runtime* jars. We don't want to see
*buildtime* jars in there. Which is why I thought it was great when you
decided to put Maven jars in maven.home/lib. I don't want to see these
jars, they are Maven's own internal ones. It must be transparent for me,
as a Maven user.
Does it work this way now ?
>
> > > 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.
I prefer to control what I need (see above). If you're saying it's just
a convenience done by Maven when you build it from CVS sources, then it
is fine, just as long as I can remove them afterwards and they will come
back ...
>
> > 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.
We are 100% in agreement here ... :-)
>
> 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.
yep! And there could possibly be several versions of Maven installed
locally, which is real important for building Jakarta Commons
components, right ? ;-)
Thanks
-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]>
