Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

9,836

Downloads of v 2.0.7:

135

Last Update:

18 Jan 2020

Package Maintainer(s):

Software Author(s):

  • Pivotal Software Inc.

Tags:

spring boot build script xml java development

Spring Boot CLI

This is not the latest version of Spring Boot CLI available.

  • 1
  • 2
  • 3

2.0.7 | Updated: 18 Jan 2020

Downloads:

9,836

Downloads of v 2.0.7:

135

Maintainer(s):

Software Author(s):

  • Pivotal Software Inc.

Spring Boot CLI 2.0.7

This is not the latest version of Spring Boot CLI available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Spring Boot CLI, run the following command from the command line or from PowerShell:

>

To upgrade Spring Boot CLI, run the following command from the command line or from PowerShell:

>

To uninstall Spring Boot CLI, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade spring-boot-cli -y --source="'INTERNAL REPO URL'" --version="'2.0.7'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade spring-boot-cli -y --source="'INTERNAL REPO URL'" --version="'2.0.7'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install spring-boot-cli
  win_chocolatey:
    name: spring-boot-cli
    version: '2.0.7'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'spring-boot-cli' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.0.7'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller spring-boot-cli
{
    Name     = "spring-boot-cli"
    Version  = "2.0.7"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'spring-boot-cli':
  ensure   => '2.0.7',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 18 Jan 2020.

Description

Spring Boot is a Java API and
toolset. Spring Boot makes it easy
to create stand-alone, production-grade Spring based
Applications that you can "just run".

This package will install the Spring Boot CLI distribution to
%ChocolateyInstall%\lib\spring-boot-cli and set the environment variable
SPRING_HOME pointing to the install location.

Issues

Please report any issues with this package at
https://github.com/pgalbraith/chocolatey-packages.


spring-2.0.7.RELEASE\bin\spring
 
spring-2.0.7.RELEASE\bin\spring.bat
@if "%DEBUG%" == "" @echo off

@rem Set local scope for the variables with windows NT shell
if "%OS%"=="Windows_NT" setlocal

:setSpringHome
@rem Setup SPRING_HOME if not already defined
if defined SPRING_HOME goto setJavaHome
set DIRNAME=%~dp0
if "%DIRNAME%" == "" set DIRNAME=.
set SPRING_HOME=%DIRNAME%\..

:setJavaHome
@rem Find java.exe
if defined JAVA_HOME goto findJavaFromJavaHome
set JAVA_EXE=java.exe
%JAVA_EXE% -version >NUL 2>&1
if "%ERRORLEVEL%" == "0" goto runSpring
echo.
echo ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.
echo.
echo Please set the JAVA_HOME variable in your environment to match the
echo location of your Java installation.
goto fail

:findJavaFromJavaHome
set JAVA_HOME=%JAVA_HOME:"=%
set JAVA_EXE=%JAVA_HOME%/bin/java.exe
if exist "%JAVA_EXE%" goto runSpring
echo.
echo ERROR: JAVA_HOME is set to an invalid directory: %JAVA_HOME%
echo.
echo Please set the JAVA_HOME variable in your environment to match the
echo location of your Java installation.
goto fail

:runSpring
@rem Get command-line arguments, handling Windows variants

if not "%OS%" == "Windows_NT" goto win9xME_args
if "%@eval[2+2]" == "4" goto 4NT_args

:win9xME_args
@rem Slurp the command line arguments.
set CMD_LINE_ARGS=
set _SKIP=2

:win9xME_args_slurp
if "x%~1" == "x" goto execute

set CMD_LINE_ARGS=%*
goto execute

:4NT_args
@rem Get arguments from the 4NT Shell from JP Software
set CMD_LINE_ARGS=%$

:execute
@rem Setup the command line

set CLASSPATH=%SPRING_HOME%\lib\*
"%JAVA_EXE%" %JAVA_OPTS% -cp "%CLASSPATH%" org.springframework.boot.loader.JarLauncher %CMD_LINE_ARGS%

:end
@rem End local scope for the variables with windows NT shell
if "%ERRORLEVEL%"=="0" goto mainEnd

:fail
rem Set variable SPRING_EXIT_CONSOLE if you need the _script_ return code instead of
rem the _cmd.exe /c_ return code!
if  not "" == "%SPRING_EXIT_CONSOLE%" exit 1
exit /b 1

:mainEnd
if "%OS%"=="Windows_NT" endlocal

spring-2.0.7.RELEASE\INSTALL.txt
SPRING BOOT CLI - INSTALLATION
==============================

Thank you for downloading the Spring Boot CLI tool. Please follow these instructions
in order to complete your installation.


Prerequisites
-------------
Spring Boot CLI requires Java JDK v1.8 or above in order to run. Groovy v2.4.15
is packaged as part of this distribution, and therefore does not need to be installed (any
existing Groovy installation is ignored).

The CLI will use whatever JDK it finds on your path, to check that you have an appropriate
version you should run:

	java -version

Alternatively, you can set the JAVA_HOME environment variable to point a suitable JDK.


Environment Variables
---------------------
No specific environment variables are required to run the CLI, however, you may want to
set SPRING_HOME to point to a specific installation. You should also add SPRING_HOME/bin
to your PATH environment variable.


Shell Completion
----------------
Shell auto-completion scripts are provided for BASH and ZSH. Add symlinks to the appropriate
location for your environment. For example, something like:

  ln -s ./shell-completion/bash/spring /etc/bash_completion.d/spring
  ln -s ./shell-completion/zsh/_spring /usr/local/share/zsh/site-functions/_spring


Checking Your Installation
--------------------------
To test if you have successfully installed the CLI you can run the following command:

	spring --version


spring-2.0.7.RELEASE\legal\open_source_licenses.txt
open_source_licenses.txt

Spring Boot CLI
==================================================================

Pivotal makes available all content in this download ("Content").
Unless otherwise indicated below, the Content is provided to you under
the terms and conditions of the Apache License 2.0 (the "License"). A
copy of the license is available in the file called LICENSE.txt or you
 may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

The following copyright statements and licenses apply to various open
source software packages (or portions thereof) that are distributed with
this content.


=================================================================
TABLE OF CONTENTS
=================================================================


The following is a listing of the open source components detailed in this
document.  This list is provided for your convenience; please read further if
you wish to review the copyright notice(s) and the full text of the license
associated with each component.


SECTION 1: BSD-STYLE, MIT-STYLE, OR SIMILAR STYLE LICENSES

   >>> JLine (jline:jline)
   >>> JOpt Simple (net.sf.jopt-simple:jopt-simple)
   >>> ASM 4.0 (org.ow2.asm:asm)


SECTION 2: Apache License, V2.0

   >>> JSON library from Android SDK (com.vaadin.external.google:android-json)
   >>> Apache Commons Codec (commons-codec:commons-codec)
   >>> Apache HttpClient (org.apache.httpcomponents:httpclient)
   >>> Apache HttpCore (org.apache.httpcomponents:httpcore)
   >>> Plexus Cipher: encryption/decryption Component (org.sonatype.plexus:plexus-cipher)
   >>> Plexus Security Dispatcher Component (org.sonatype.plexus:plexus-sec-dispatcher)
   >>> Apache Commons Logging (commons-logging:commons-logging)
   >>> Apache Groovy (org.codehaus.groovy:groovy)
   >>> Maven Aether Provider (org.apache.maven:maven-aether-provider)
   >>> Maven Model (org.apache.maven:maven-model)
   >>> Maven Model Builder (org.apache.maven:maven-model-builder)
   >>> Maven Repository Metadata Model (org.apache.maven:maven-repository-metadata)
   >>> Maven Settings (org.apache.maven:maven-settings)
   >>> Maven Settings Builder (org.apache.maven:maven-settings-builder)
   >>> Plexus :: Component Annotations (org.codehaus.plexus:plexus-component-annotations)
   >>> Plexus Common Utilities (org.codehaus.plexus:plexus-utils)
   >>> Plexus Component API (org.codehaus.plexus:plexus-component-api)
   >>> Plexus Interpolation API (org.codehaus.plexus:plexus-interpolation)


SECTION 3: Eclipse Public License, Version 1.0

   >>> Aether API (org.eclipse.aether:aether-api)
   >>> Aether Connector Basic (org.eclipse.aether:aether-connector-basic)
   >>> Aether Implementation (org.eclipse.aether:aether-impl)
   >>> Aether SPI (org.eclipse.aether:aether-spi)
   >>> Aether Transport File (org.eclipse.aether:aether-transport-file)
   >>> Aether Transport HTTP (org.eclipse.aether:aether-transport-http)
   >>> Aether Utilities (org.eclipse.aether:aether-util)



--------------- SECTION 1:  BSD-STYLE, MIT-STYLE, OR SIMILAR STYLE LICENSES ----------

BSD-STYLE, MIT-STYLE, OR SIMILAR STYLE LICENSES are applicable to the following component(s).


>>> JLine (jline:jline)

Copyright (c) 2002-2006, Marc Prud'hommeaux <[email protected]>
All rights reserved.

Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with
the distribution.

Neither the name of JLine nor the names of its contributors
may be used to endorse or promote products derived from this
software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.


>>> net.sf.jopt-simple:jopt-simple:4.5

The MIT License (MIT)

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.


>>> org.ow2.asm:asm

Copyright (c) 2000-2011 INRIA, France Telecom
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.

3. Neither the name of the copyright holders nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.



--------------- SECTION 2: Apache License, V2.0 ----------

Apache License, V2.0 is applicable to the following component(s).


>>> org.apache.httpcomponents:httpclient
>>> org.apache.httpcomponents:httpcore
>>> org.sonatype.plexus:plexus-cipher
>>> org.sonatype.plexus:plexus-sec-dispatcher
>>> commons-logging:commons-logging
>>> org.codehaus.groovy:groovy
>>> org.apache.maven:maven-aether-provider
>>> org.apache.maven:maven-model
>>> org.apache.maven:maven-model-builder
>>> org.apache.maven:maven-repository-metadata
>>> org.apache.maven:maven-settings
>>> org.apache.maven:maven-settings-builder
>>> org.codehaus.plexus:plexus-component-annotations
>>> org.codehaus.plexus:plexus-utils
>>> org.codehaus.plexus:plexus-component-api
>>> org.codehaus.plexus:plexus-interpolation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License

>>> CGLIB 3.0 (cglib:cglib:3.0):

Per the LICENSE file in the CGLIB JAR distribution downloaded from
http://sourceforge.net/projects/cglib/files/cglib3/3.0/cglib-3.0.jar/download,
CGLIB 3.0 is licensed under the Apache License, version 2.0, the text of which
is included above.


--------------- SECTION 3: Eclipse Public License, Version 1.0 ----------

Eclipse Public License, Version 1.0 is applicable to the following component(s).

>>> org.eclipse.aether:aether-api
>>> org.eclipse.aether:aether-connector-basic
>>> org.eclipse.aether:aether-impl
>>> org.eclipse.aether:aether-spi
>>> org.eclipse.aether:aether-transport-file
>>> org.eclipse.aether:aether-transport-http
>>> org.eclipse.aether:aether-util

The Eclipse Foundation makes available all content in this plug-in ("Content").
Unless otherwise  indicated below, the Content is provided to you under the terms
and conditions  of the Eclipse Public License Version 1.0 ("EPL").  A copy of the
EPL is available  at http://www.eclipse.org/legal/epl-v10.html.

For purposes of the EPL, "Program" will mean the Content.

If you did not receive this Content directly from the Eclipse Foundation, the
Content is  being redistributed by another party ("Redistributor") and different
terms and conditions may apply to your use of any object code in the Content.
Check the Redistributor's license that was provided with the Content.  If no such
license exists, contact the Redistributor.  Unless otherwise indicated below, the
terms and conditions of the EPL still apply to any source code in the Content and
such source code may be obtained at http://www.eclipse.org/



===========================================================================

To the extent any open source subcomponents are licensed under the EPL and/or
other similar licenses that require the source code and/or modifications to
source code to be made available (as would be noted above), you may obtain a
copy of the source code corresponding to the binaries for such open source
components and modifications thereto, if any, (the "Source Files"), by
downloading the Source Files from https://github.com/spring-projects/spring-boot,
or by sending a request, with your name and address to:

    Pivotal, Inc., 875 Howard St,
    San Francisco, CA 94103
    United States of America

or email [email protected].  All such requests should clearly specify:

    OPEN SOURCE FILES REQUEST
    Attention General Counsel
spring-2.0.7.RELEASE\lib\spring-boot-cli-2.0.7.RELEASE.jar
 
spring-2.0.7.RELEASE\LICENCE.txt
Copyright 2012-2013 the original author or authors.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

spring-2.0.7.RELEASE\shell-completion\bash\spring
 
spring-2.0.7.RELEASE\shell-completion\zsh\_spring
 
tools\chocolateyInstall.ps1
$toolsDir = Split-Path $MyInvocation.MyCommand.Definition
$spring_home = Join-Path $env:ChocolateyPackageFolder "spring-2.0.7.RELEASE"

Install-ChocolateyEnvironmentVariable "SPRING_HOME" "$spring_home" Machine
Install-BinFile "spring" "$spring_home\bin\spring.bat"
tools\chocolateyUninstall.ps1
$toolsDir = Split-Path $MyInvocation.MyCommand.Definition
$spring_home = Join-Path $env:ChocolateyPackageFolder "spring-2.0.7.RELEASE"

Uninstall-ChocolateyEnvironmentVariable "SPRING_HOME" Machine
Uninstall-BinFile "spring" "$spring_home\bin\spring.bat"
tools\LICENSE.txt
Copyright 2012-2013 the original author or authors.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
tools\VERIFICATION.txt
To verify, compare with the binary from the vendor's official distribution point:

https://docs.spring.io/spring-boot/docs/2.0.7.RELEASE/reference/html/getting-started-installing-spring-boot.html#getting-started-manual-cli-installation

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Spring Boot CLI 2.7.3 1464 Wednesday, September 21, 2022 Approved
Spring Boot CLI 2.2.4 2420 Tuesday, January 21, 2020 Approved
Spring Boot CLI 2.2.3 173 Saturday, January 18, 2020 Approved
Spring Boot CLI 2.2.2 243 Thursday, December 26, 2019 Approved
Spring Boot CLI 2.2.1 307 Wednesday, November 20, 2019 Approved
Spring Boot CLI 2.2.0 135 Wednesday, November 20, 2019 Approved
Spring Boot CLI 2.1.12 147 Saturday, January 18, 2020 Approved
Spring Boot CLI 2.1.11 164 Thursday, December 26, 2019 Approved
Spring Boot CLI 2.1.10 147 Wednesday, November 20, 2019 Approved
Spring Boot CLI 2.1.9 315 Friday, October 11, 2019 Approved
Spring Boot CLI 2.1.8 257 Monday, September 16, 2019 Approved
Spring Boot CLI 2.1.7 319 Tuesday, August 6, 2019 Approved
Spring Boot CLI 2.1.6 271 Friday, July 5, 2019 Approved
Spring Boot CLI 2.1.5 308 Sunday, May 19, 2019 Approved
Spring Boot CLI 2.1.4 320 Monday, April 22, 2019 Approved
Spring Boot CLI 2.1.3 366 Saturday, February 16, 2019 Approved
Spring Boot CLI 2.1.2 257 Thursday, January 17, 2019 Approved
Spring Boot CLI 2.1.1 261 Tuesday, December 18, 2018 Approved
Spring Boot CLI 2.1.0 287 Thursday, November 15, 2018 Approved
Spring Boot CLI 2.0.9 141 Saturday, January 18, 2020 Approved
Spring Boot CLI 2.0.8 200 Saturday, January 18, 2020 Approved
Spring Boot CLI 2.0.7 135 Saturday, January 18, 2020 Approved
Spring Boot CLI 2.0.6 150 Saturday, January 18, 2020 Approved
Spring Boot CLI 2.0.5 354 Friday, September 14, 2018 Approved
Spring Boot CLI 2.0.4 381 Sunday, August 26, 2018 Approved
Spring Boot CLI 1.5.22 156 Saturday, January 18, 2020 Approved
Discussion for the Spring Boot CLI Package

Ground Rules:

  • This discussion is only about Spring Boot CLI and the Spring Boot CLI package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Spring Boot CLI, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus