Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

setup windows bootstrap 

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@345015 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Leslie Porter 2005-11-16 13:40:42 +00:00
parent aa06bb1188
commit 68d386c4b9
1 changed files with 22 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
m2-bootstrap-all.bat → bootstrap.bat
View File

@ -101,34 +101,39 @@ goto Win9xApp
@REM Reaching here means variables are defined and arguments have been captured @REM Reaching here means variables are defined and arguments have been captured
:endInit :endInit
SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe" SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe"
SET MAVEN_OPTS=%MAVEN_OPTS% -Dmaven.home="%M2_HOME%"
@REM Build MBoot2 @REM Build MBoot2
cd maven-mboot2 cd bootstrap\bootstrap-mini
call .\build call .\build
@REM Build Maven2 @REM Build Maven2
cd .. cd ..
%MAVEN_JAVA_EXE% %MAVEN_OPTS% -jar mboot.jar %MAVEN_CMD_LINE_ARGS% %MAVEN_JAVA_EXE% %MAVEN_OPTS% -jar target\bootstrap-mini.jar install %MAVEN_CMD_LINE_ARGS%
@REM I Really Don't want to be rebuilding these (Especially the reports) every time, but cd bootstrap\bootstrap-installer
@REM until we regularly push them to the repository and the integration tests rely on %MAVEN_JAVA_EXE% %MAVEN_OPTS% -jar ..\bootstrap-installer.jar package %MAVEN_CMD_LINE_ARGS%
@REM some of these plugins, there is no choice
echo
echo -----------------------------------------------------------------------
echo Rebuilding maven2 plugins
echo -----------------------------------------------------------------------
@REM Build plugin plugin first, it seems to choke on the version built by the bootstrap
cd maven-plugins\maven-plugin-plugin
call mvn --no-plugin-registry --batch-mode --fail-at-end -e %MAVEN_CMD_LINE_ARGS% clean:clean install
cd ..\.. cd ..\..
cd maven-plugins set PLUGINS_DIR=..\plugins
@REM update the release info to ensure these versions get used in the integration tests if exist "%PLUGINS_DIR%\pom.xml" goto setArgs
call mvn --no-plugin-registry --batch-mode -DupdateReleaseInfo=true -e %MAVEN_CMD_LINE_ARGS% clean:clean install
set BUILD_ARGS=%MAVEN_CMD_LINE_ARGS%
goto doBuild
:setArgs
set BUILD_ARGS=%MAVEN_CMD_LINE_ARGS% --build-plugins --plugins-directory=%PLUGINS_DIR%
:doBuild
REM TODO: get rid of M2_HOME once integration tests are in here
%MAVEN_JAVA_EXE% %MAVEN_OPTS% -jar bootstrap\bootstrap-installer\target\bootstrap-installer.jar --prefix=%M2_HOME%\.. %BUILD_ARGS%
REM TODO: should w ebe going back to the mini now that we have the real thing?
cd maven-core-it-verifier
%MAVEN_JAVA_EXE% %MAVEN_OPTS% -jar ..\bootstrap\bootstrap-mini\target\bootstrap-mini.jar package %MAVEN_CMD_LINE_ARGS%
cd .. cd ..
echo echo