Brekke, Jeff wrote:
> The bootstrap process has evolved for developers.
> This is why we've attempted to package installations up separately.
> I use the bootstrap target as a convenience step when updating maven
> from cvs multiple times a day.
>
> The idea of a built-in installation/update mechanism of maven has
> already been started. Jason started targets that will update
> the locally installed version of maven when a new one is present,
> and we have update targets for the project object model also.
>
> The lib.repo wasn't supposed to be used as a temporary directory
> but the local repo for jars that projects need to depend on.
> Just move lib.repo out from under where you install maven?
Honestly, IMO, maven.home should not be treated as a temporary
directory either. That is why I posted what I did.
Another possibility is dynamically change lib.repo in the bootstrap.
I.e. the bootstrap starts with a local lib.repo, and after it starts
installing the maven directory, it sets up the production lib.repo.
I'm also thinking of integrating with GUMP--avoiding circular
dependancies. (I.e. libraries that Maven uses are built with
Maven).
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
