bootstrap is to create a new maven installation without needing maven installed, you still need M2_HOME pointing to where you want maven to be installed. It also works when you already have a woring installation, removing it and installing again (not using it for building)
If you just want to build the jars or install them you can use a released version of maven, maven core is just another maven project. On 3/15/06, Szczepan Faber <[EMAIL PROTECTED]> wrote: > Hi, > > According to FAQ info on > http://maven.apache.org/guides/development/guide-building-m2.html, > in order to build M2, you should set env variables to point to new > installation of M2. > > set M2_HOME=c:\maven-2.0.1-SNAPSHOT > set PATH=%M2_HOME%\bin;%PATH% > > But when you set those variables, the script file (bootstrap.bat/sh) > does not work any more - because you don't have M2_HOME pointed to > working installation of M2. If you decide that script creates new > installation of maven, the script should not depend on existing maven. > I believe the user does not want to install new maven snapshot - he > wants just compile and create jars. Then if the user wants it, he can > install jars, set up the env. variables to have his development env > working on brand new created maven. > > Now, I don't know if I can fire the bootstrap script with my existing > maven - according to the documentation it will install new M2 into > M2_HOME, which is not what I want. > > Thanks, > Szczepan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
