breadlicker45/batch-stack-code · Datasets at Hugging Face

text stringlengths 0 834k
if %0X==X goto COMMON_BUILD
if .%1==.--verbose shift & set ""CB_VERBOSE=true""
if .%1==.--silent shift & set ""CB_INSTALL_USER_COMMIT=false"" & set ""CB_INSTALL_SILENT=true""
if .%1==.--force shift & set ""CB_INSTALL_OVERWRITE_DIST=true""
if .%1==.--default shift & set CB_SET_DEFAULT=true
if .%1==.--offline shift & set ""CB_OFFLINE=true""
if .%1==.-h goto HELP
if .%1==.--help goto HELP
if .%1==.-v goto VERSION
if .%1==.--version goto VERSION
if .%1==.-new shift & goto PROJECT_WIZARD
if .%1==.--new shift & goto PROJECT_WIZARD
if .%1==.-exp shift & goto PROJECT_EXPLORE
if .%1==.--explore shift & goto PROJECT_EXPLORE
if .%1==.--packages shift & goto PACKAGES
if .%1==.--setenv shift & goto SET_ENV
if .%1==.--install shift & goto INSTALL_CB
if .%1==.--java goto SET_JAVA_PARAM
set CB_PARAMETERS=%CB_PARAMETERS% %~1
::if "".%CB_PARAMETERS%""==""."" (set CB_PARAMETERS=%~1) else (set CB_PARAMETERS=%CB_PARAMETERS% %~1)
shift
goto CHECK_PARAMETER

:SET_JAVA_PARAM
echo %2 > %CB_JAVA_VERSION_FILE%
shift
shift
goto CHECK_PARAMETER


:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:HELP
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
echo %PN% - common build v%CB_VERSION%
echo usage: %PN% [OPTION]
echo.
echo Overview of the available OPTIONs:
echo -h, --help Show this help message.
echo -v, --version Print the version information.
echo --new Create a new project. You can prefill wizard settings
echo by setting the corresponding entries as parameter, e.g.
echo --new 1 my-project my.root.pkg my my
echo --java [version] Set a different java version for this run, e.g. --java 14.
echo --silent Suppress the console output from the common-build.
echo --force Flag to force new installtion.
echo --offline Set the offline mode; it will be detect automatically.
echo --install [pkg] Install the a software package. Optionally you can set the
echo version number (does not work for every package); otherwise
echo the default version number is used (from the configuration
echo file tool-version-default.properties)
echo Additionally a parameter -d or --default marks this version
echo as default.
echo --packages Shows the supported packages.
echo -exp, --explore Starts the file explorer with the current path.
echo --setenv Set all internal used environment variables.
echo.
echo Environment variable:
echo CB_DEVTOOLS Defines the devtools directory, default c:\devtools.
echo CB_HOME Defines the home environment, default %%CB_DEVTOOLS%%\cb.
echo.
echo Special files:
echo .java-version Can be used to refer to a specific java version, e.g. 11
echo.
echo Customizing:
echo CB_CUSTOM_SETTING The common build is flexible. You can define a script which
echo that is called as a hook for all operations. You can find an
echo example sciipt in %%CB_HOME%%\bin\sample\cb-custom-sample.bat
echo CB_CUSTOM_CONFIG For complete customizing of the common build you can create
echo a custom config project. This can be done by cb --new (select
echo Common Config Home project). After customizing (see further
echo information on the web) and publishing it as a git project,
echo you can refer the git url to the CB_CUSTOM_CONFIG environment
echo variable. The VERSION file is mainly the reference for updates
echo of the project (as default daily check, can be configured).
echo The project is checkout in .common-buik/conf/[domain-unique
echo -name] inside the home folder (Windows %USERPROFILE%, others
echo $HOME. Alternatively, instead of the environment variable,
echo a file .common-build\conf\.cb-custom-config containing the
echo git url can be used.""
echo.
echo CB_PACKAGE_URL To support software packages outside the common build, you
echo can define an URL that covers a directory of zip files.
echo CB_PACKAGE_USER The user for accessing the CB_PACKAGE_URL.
echo CB_PACKAGE_PASSWORD In case the value is ask, the password can be entered securely
echo on the command line.
call %CB_SCRIPT_PATH%include\how-to.bat 2>nul
goto END


:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:VERSION
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
echo %CB_LINE%
echo toolarium common build %CB_VERSION%
echo.
echo %CB_LINEHEADER%Installed tool versions:
for /f ""tokens=1,* delims=^="" %%i in ('type %CB_TOOL_VERSION_INSTALLED%') do (echo -%%i: %%j)
echo %CB_LINE%
goto END

if %0X==X goto COMMON_BUILD

if .%1==.--verbose shift & set ""CB_VERBOSE=true""

if .%1==.--silent shift & set ""CB_INSTALL_USER_COMMIT=false"" & set ""CB_INSTALL_SILENT=true""

if .%1==.--force shift & set ""CB_INSTALL_OVERWRITE_DIST=true""

if .%1==.--default shift & set CB_SET_DEFAULT=true

if .%1==.--offline shift & set ""CB_OFFLINE=true""

if .%1==.-h goto HELP

if .%1==.--help goto HELP

if .%1==.-v goto VERSION

if .%1==.--version goto VERSION

if .%1==.-new shift & goto PROJECT_WIZARD

if .%1==.--new shift & goto PROJECT_WIZARD

if .%1==.-exp shift & goto PROJECT_EXPLORE

if .%1==.--explore shift & goto PROJECT_EXPLORE

if .%1==.--packages shift & goto PACKAGES

if .%1==.--setenv shift & goto SET_ENV

if .%1==.--install shift & goto INSTALL_CB

if .%1==.--java goto SET_JAVA_PARAM

set CB_PARAMETERS=%CB_PARAMETERS% %~1

::if "".%CB_PARAMETERS%""==""."" (set CB_PARAMETERS=%~1) else (set CB_PARAMETERS=%CB_PARAMETERS% %~1)

shift

goto CHECK_PARAMETER

:SET_JAVA_PARAM

echo %2 > %CB_JAVA_VERSION_FILE%

shift

goto CHECK_PARAMETER

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:HELP

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

echo %PN% - common build v%CB_VERSION%

echo usage: %PN% [OPTION]

echo.

echo Overview of the available OPTIONs:

echo -h, --help Show this help message.

echo -v, --version Print the version information.

echo --new Create a new project. You can prefill wizard settings

echo by setting the corresponding entries as parameter, e.g.

echo --new 1 my-project my.root.pkg my my

echo --java [version] Set a different java version for this run, e.g. --java 14.

echo --silent Suppress the console output from the common-build.

echo --force Flag to force new installtion.

echo --offline Set the offline mode; it will be detect automatically.

echo --install [pkg] Install the a software package. Optionally you can set the

echo version number (does not work for every package); otherwise

echo the default version number is used (from the configuration

echo file tool-version-default.properties)

echo Additionally a parameter -d or --default marks this version

echo as default.

echo --packages Shows the supported packages.

echo -exp, --explore Starts the file explorer with the current path.

echo --setenv Set all internal used environment variables.

echo.

echo Environment variable:

echo CB_DEVTOOLS Defines the devtools directory, default c:\devtools.

echo CB_HOME Defines the home environment, default %%CB_DEVTOOLS%%\cb.

echo.

echo Special files:

echo .java-version Can be used to refer to a specific java version, e.g. 11

echo.

echo Customizing:

echo CB_CUSTOM_SETTING The common build is flexible. You can define a script which

echo that is called as a hook for all operations. You can find an

echo example sciipt in %%CB_HOME%%\bin\sample\cb-custom-sample.bat

echo CB_CUSTOM_CONFIG For complete customizing of the common build you can create

echo a custom config project. This can be done by cb --new (select

echo Common Config Home project). After customizing (see further

echo information on the web) and publishing it as a git project,

echo you can refer the git url to the CB_CUSTOM_CONFIG environment

echo variable. The VERSION file is mainly the reference for updates

echo of the project (as default daily check, can be configured).

echo The project is checkout in .common-buik/conf/[domain-unique

echo -name] inside the home folder (Windows %USERPROFILE%, others

echo $HOME. Alternatively, instead of the environment variable,

echo a file .common-build\conf\.cb-custom-config containing the

echo git url can be used.""

echo.

echo CB_PACKAGE_URL To support software packages outside the common build, you

echo can define an URL that covers a directory of zip files.

echo CB_PACKAGE_USER The user for accessing the CB_PACKAGE_URL.

echo CB_PACKAGE_PASSWORD In case the value is ask, the password can be entered securely

echo on the command line.

call %CB_SCRIPT_PATH%include\how-to.bat 2>nul

goto END

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:VERSION

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

echo %CB_LINE%

echo toolarium common build %CB_VERSION%

echo.

echo %CB_LINEHEADER%Installed tool versions:

for /f ""tokens=1,* delims=^="" %%i in ('type %CB_TOOL_VERSION_INSTALLED%') do (echo -%%i: %%j)

echo %CB_LINE%

goto END