> > You should've gotten a deprecation warning for having ${lib.repo} and
> > not ${maven.repo.local}.
> >
>
> No, there is no warning at all. In addition if you check
> build-bootstrap.xml, you'll see there are references to lib.repo
> everywhere but none to maven.repo.local.
Yah, once build-bootstrap.xml <exec>'s the maven[.bat], then
maven should complain about lib.repo instead of maven.repo.local.
> I have tried setting only maven.repo.local in my build.properties but
> then Maven bootstrap does not use it and default to user.home/maven.repo
I reckon we need both, until we fix the bootstrap to use lib.repo.
Transitions always suck.
> Try setting it to a different directory to see if it has any effect, as
> the default is what you are using.
Will do.
> yeah, although a project local build.properties is there for that reason
> too, right ?
Hmm... Well, once again, we've got to find maven.jar before we can
read the properties files (any of them) at this point. So, we can't
have maven.home set in a properties file.
> BTW, are you confirming that build.properties (either in $HOME or
> project local) is still used by Maven ng (i.e. not only by the
> bootstrap) ?
$HOME/build.properties
$PROJECT/build.properties
$PROJECT/project.properties
They are all still read.
-bob
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
