Downloads of v 3.7.3:


Last Update:

31 Mar 2016

Package Maintainer(s):

Software Author(s):

  • Rubén Bresler


sts eclipse ide jdk8 springframework

STS (Install)

This is not the latest version of STS (Install) available.

  • 1
  • 2
  • 3

3.7.3 | Updated: 31 Mar 2016



Downloads of v 3.7.3:



Software Author(s):

  • Rubén Bresler

  • 1
  • 2
  • 3
STS (Install) 3.7.3

This is not the latest version of STS (Install) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install STS (Install), run the following command from the command line or from PowerShell:


To upgrade STS (Install), run the following command from the command line or from PowerShell:


To uninstall STS (Install), 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

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 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 springtoolsuite -y --source="'INTERNAL REPO URL'" --version="'3.7.3'" [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 springtoolsuite -y --source="'INTERNAL REPO URL'" --version="'3.7.3'" 

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

Exit $exitCode

- name: Install springtoolsuite
    name: springtoolsuite
    version: '3.7.3'
    state: present

See docs at

chocolatey_package 'springtoolsuite' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.7.3'

See docs at

cChocoPackageInstaller springtoolsuite
    Name     = "springtoolsuite"
    Version  = "3.7.3"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'springtoolsuite':
  ensure   => '3.7.3',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator ferventcoder on 01 Apr 2016.


The Spring Tool Suite is an Eclipse-based development environment that is customized for developing Spring applications. It provides a ready-to-use environment to implement, debug, run, and deploy your Spring applications, including integrations for Pivotal tc Server, Pivotal Cloud Foundry, Git, Maven, AspectJ, and comes on top of the latest Eclipse releases.

### Bugs and Features:

Create an issue or comment to an existing one -

$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName= 'SpringToolSuite' # arbitrary name for the package, used in messages
$packageVersion = '3.7.3'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = "$packageVersion.RELEASE/dist/e4.6/spring-tool-suite-$"
$url64      = "$packageVersion.RELEASE/dist/e4.6/spring-tool-suite-$"

$global:installLocation = "C:\tools\SpringToolSuite\v$packageVersion"

$checksum64     = "58866072800a185168b1827963660f7d8eb134b5"

Write-Host "$toolsDir"
Write-Host "$(Split-Path -Leaf $url64)"

if(!$PSScriptRoot){ $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent }
. "$PSScriptRoot\UtilFunctions.ps1"

Install-ZipPackage $packageName $url $global:installLocation $url64 -specificFolder "sts-bundle\sts-$packageVersion.RELEASE\*" -checksum64 "$checksum64" -checksumType64 "sha1"
$finalLocation = $(Join-Path $global:installLocation "STS")
Move-Item $(Join-Path $global:installLocation "sts-bundle\sts-$packageVersion.RELEASE") $finalLocation -Force
Remove-Item $(Join-Path $global:installLocation "sts-bundle") -Force -Recurse
WriteInstalledFiles $global:installLocation

$stsExecutable = $(Join-Path $finalLocation "STS.exe")
Install-ChocolateyDesktopLink "$stsExecutable"
Install-ChocolateyPinnedTaskBarItem "$stsExecutable"
$packageName = 'STS'

if(!$PSScriptRoot){ $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent }
. "$PSScriptRoot\UtilFunctions.ps1"

Uninstall-ZipPackage "$packageName"

Uninstall-DesktopLinkAndPinnedTaskBarItem "$packageName"
Uninstall-DesktopLinkAndPinnedTaskBarItem "$packageName"
## Summary
How do I create packages? See

If you are submitting packages to the community feed (
always try to ensure you have read, understood and adhere to the create
packages wiki link above.

## Automatic Packages?
Consider making this package an automatic package, for the best 
maintainability over time. Read up at

## Shim Generation
Any executables you include in the package or download (but don't call 
install against using the built-in functions) will be automatically shimmed.

This means those executables will automatically be included on the path.
Shim generation runs whether the package is self-contained or uses automation 

By default, these are considered console applications. 

If the application is a GUI, you should create an empty file next to the exe 
named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.

If you want to ignore the executable, create an empty file next to the exe 
named 'name.exe.ignore' e.g. 'bob.exe' would need a file named 

## Self-Contained? 
If you have a self-contained package, you can remove the automation scripts 
entirely and just include the executables, they will automatically get shimmed, 
which puts them on the path. Ensure you have the legal right to distribute 
the application though. See 

You should read up on the Shim Generation section to familiarize yourself 
on what to do with GUI applications and/or ignoring shims.

## Automation Scripts
You have a powerful use of Chocolatey, as you are using PowerShell. So you
can do just about anything you need. Choco has some very handy built-in 
functions that you can use, these are sometimes called the helpers.

### Built-In Functions

A note about a couple:
* Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder. 
* Install-BinFile - used for non-exe files - executables are automatically shimmed...
* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed

### Getting package specific information
Use the package parameters pattern - see

### Need to mount an ISO?

### Environment Variables
Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow):

 * TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
 * ChocolateyInstall = Top level folder where Chocolatey is installed
 * chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
 * chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
 * chocolateyPackageFolder = The top level location of the package folder

#### Advanced Environment Variables
The following are more advanced settings:

 * chocolateyPackageParameters = (
 * CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
    - Otherwise take a dependency on the specific version you need. 
 * chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
    - Automatically handled in built in Choco functions. 
 * OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
 * OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
 * OS_NAME = The reported name of the OS. (0.9.9+)
 * IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)
#### Experimental Environment Variables
The following are experimental or use not recommended:

 * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
 * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
    - it's based on git describe
 * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
 * chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
 * chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)

function Parse-Parameters {
	$arguments = @{};
	$packageParameters = $env:chocolateyPackageParameters;

	if($packageParameters) {
		Write-Host "PackageParameters: $packageParameters"
		$MATCH_PATTERN = "/([a-zA-Z]+)=(.*)"
		if($packageParameters -match $MATCH_PATTERN){
			$results = $packageParameters | Select-String $MATCH_PATTERN -AllMatches 
			$results.matches | % { 
		} else {
			Write-Host "Default packageParameters will be used"
		if($arguments.ContainsKey("InstallLocation")) {
			$global:installLocation = $arguments["InstallLocation"];
			Write-Host "Value variable installLocation changed to $global:installLocation"
		} else {
			Write-Host "Default InstallLocation will be used"
	} else {
		Write-Host "Package parameters will not be overwritten"

function Uninstall-ZipPackage {
  [string] $packageName
	if(!$packageName) {
		Write-ChocolateyFailure "Uninstall-ZipPackage" "Missing PackageName input parameter."
	ChildItem "$env:ChocolateyInstall\lib\${packageName}" -Recurse -Filter "${packageName}" | 
	ForEach-Object{ $installLocation = (Get-Content $_.FullName | Select-Object -First 1);
		if (("$installLocation" -match "${packageName}|apache-tomcat") -and (Test-Path -Path "$installLocation")) {
			Write-Host "Uninstalling by removing directory $installLocation";
			Remove-Item -Recurse -Force "$installLocation"
		} else {
			Write-ChocolateyFailure "Uninstall-ZipPackage" "Unable to delete directory: $installLocation"

function Uninstall-DesktopLinkAndPinnedTaskBarItem {
	[string] $packageName

	$pinnedLink="${env:USERPROFILE}\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar\${packageName}.lnk"

	if(!$packageName) {
		throw "Missing PackageName input parameter."

	If (Test-Path "$desktopLink") {
		Remove-Item $desktopLink
		'desktoplink removed'
	If (Test-Path "$pinnedLink") {
		Remove-Item $pinnedLink
		'pinnedlink removed'

# Issue
function Get-Unzip {
Unzips an archive and returns the location for further processing.

Unzips an archive using the 7za command line tool.

The full path to your archive.

.PARAMETER Destination
A directory where you would like the unzipped files to end up.

.PARAMETER SpecificFolder
OPTIONAL - A specific directory or glob pattern within the archive to extract.

.PARAMETER PackageName
OPTIONAL - This will faciliate logging unzip activity for subsequent uninstall.

$scriptPath = (Split-Path -parent $MyInvocation.MyCommand.Definition)
Get-ChocolateyUnzip "c:\" $scriptPath somedirinzip\somedirinzip

Returns the passed in $destination.

This helper reduces the number of lines one would have to write to unzip a file to 1 line.
There is no error handling built into this method.
  [string] $fileFullPath,
  [string] $destination,
  [string] $specificFolder,
  [string] $packageName
  Write-Debug "Running 'Get-ChocolateyUnzip' with fileFullPath:'$fileFullPath', destination:'$destination'";

  if ($packageName) {
    if (!(Test-Path -path $packagelibPath)) {
      New-Item $packagelibPath -type directory

    $zipFilename=split-path $fileFullPath -Leaf
    $zipExtractLogFullPath=join-path $packagelibPath $zipFilename`.txt

  Write-Host "Extracting $fileFullPath to $destination..."
  if (![System.IO.Directory]::Exists($destination)) {[System.IO.Directory]::CreateDirectory($destination)}

  # On first install, env:ChocolateyInstall might be null still - join-path has issues
  $7zip = Join-Path "$env:SystemDrive" 'chocolatey\tools\7za.exe'
  if ($env:ChocolateyInstall){
    $7zip = Join-Path "$env:ChocolateyInstall" 'tools\7za.exe'

  if ($zipExtractLogFullPath) {
    $unzipOps = "Start-Process `"$7zip`" -ArgumentList `"x `"`"$fileFullPath`"`" -o`"`"$destination`"`" `"`"$specificFolder`"`" -y`" -Wait -Windowstyle Hidden"
    $scriptBlock = [scriptblock]::create($unzipOps)

    Write-FileUpdateLog $zipExtractLogFullPath $destination $scriptBlock
  } else {
    Start-Process "$7zip" -ArgumentList "x `"$fileFullPath`" -o`"$destination`" `"$specificFolder`" -y" -Wait -WindowStyle Hidden

  return $destination

# Copyright 2011 - Present RealDimensions Software, LLC & original authors/contributors from
# 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
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# See the License for the specific language governing permissions and
# limitations under the License.

function Install-ZipPackage {
Downloads and unzips a package

This will download a file from a url and unzip it on your machine.

.PARAMETER PackageName
The name of the package we want to download - this is arbitrary, call it whatever you want.
It's recommended you call it the same as your nuget package id.

This is the url to download the file from.

OPTIONAL - If there is an x64 installer to download, please include it here. If not, delete this parameter

.PARAMETER UnzipLocation
This is a location to unzip the contents to, most likely your script folder.

OPTIONAL (Right now) - This allows a checksum to be validated for files that are not local

.PARAMETER Checksum64
OPTIONAL (Right now) - This allows a checksum to be validated for files that are not local

.PARAMETER ChecksumType
OPTIONAL (Right now) - 'md5', 'sha1', 'sha256' or 'sha512' - defaults to 'md5'

.PARAMETER ChecksumType64
OPTIONAL (Right now) - 'md5', 'sha1', 'sha256' or 'sha512' - defaults to ChecksumType

.PARAMETER options
OPTIONAL - Specify custom headers

  $options =
    Headers = @{
      Accept = 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8';
      'Accept-Charset' = 'ISO-8859-1,utf-8;q=0.7,*;q=0.3';
      'Accept-Language' = 'en-GB,en-US;q=0.8,en;q=0.6';
      Cookie = '[email protected]';
      Referer = '';

  Get-ChocolateyWebFile 'ghostdoc' '' -options $options

Install-ChocolateyZipPackage '__NAME__' 'URL' "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"


This helper reduces the number of lines one would have to write to download and unzip a file to 1 line.
This method has error handling built into it.

  [string] $packageName,
  [string] $url,
  [string] $unzipLocation,
  [alias("url64")][string] $url64bit = '',
  [string] $specificFolder ="",
  [string] $checksum = '',
  [string] $checksumType = '',
  [string] $checksum64 = '',
  [string] $checksumType64 = '',
  [hashtable] $options = @{[email protected]{}}
  Write-Debug "Running 'Install-ChocolateyZipPackage' for $packageName with url:`'$url`', unzipLocation: `'$unzipLocation`', url64bit: `'$url64bit`', specificFolder: `'$specificFolder`', checksum: `'$checksum`', checksumType: `'$checksumType`', checksum64: `'$checksum64`', checksumType64: `'$checksumType64`' ";

  $fileType = 'zip'

  $chocTempDir = Join-Path $env:TEMP "chocolatey"
  $tempDir = Join-Path $chocTempDir "$packageName"
  if ($env:packageVersion -ne $null) {$tempDir = Join-Path $tempDir "$env:packageVersion"; }

  if (![System.IO.Directory]::Exists($tempDir)) {[System.IO.Directory]::CreateDirectory($tempDir) | Out-Null}
  $file = Join-Path $tempDir "$($packageName)Install.$fileType"
  Get-ChocolateyWebFile $packageName $file $url $url64bit -checkSum $checkSum -checksumType $checksumType -checkSum64 $checkSum64 -checksumType64 $checksumType64 -options $options
  Get-Unzip "$file" $unzipLocation $specificFolder $packageName

function GetFiles($path = $pwd, [string[]]$exclude) 
    foreach ($item in Get-ChildItem $path)
        if ($exclude | Where {$item -like $_}) { continue }

        if (Test-Path $item.FullName -PathType Container) 
            GetFiles $item.FullName $exclude

function WriteInstalledFiles($path) {

	$fileType = 'zip'

	$chocTempDir = Join-Path $env:TEMP "chocolatey"
	$tempDir = Join-Path $chocTempDir "$packageName"

	if ($env:packageVersion -ne $null) {$tempDir = Join-Path $tempDir "$env:packageVersion"; }

	$file = Join-Path $tempDir "$($packageName)Install.$fileType"

    if (!(Test-Path -path $packagelibPath)) {
      New-Item $packagelibPath -type directory

    $zipFilename=split-path $file -Leaf
    $zipExtractLogFullPath=join-path $packagelibPath $zipFilename`.txt

    #$scriptBlock = [scriptblock]::create("GetFiles $finalLocation")
    #Write-FileUpdateLog $zipExtractLogFullPath $path $scriptBlock

    if (Test-Path -path $zipExtractLogFullPath) {
      Remove-Item $zipExtractLogFullPath -Force
    GetFiles $Path | Add-Content $zipExtractLogFullPath

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 Tool Suite 4.14.0 15055 Wednesday, April 6, 2022 Exempted
Spring Tool Suite 4.13.1 12383 Monday, February 7, 2022 Exempted
Spring Tool Suite 4.13.0 7900 Wednesday, December 29, 2021 Exempted
Spring Tool Suite 4.12.1 45 Wednesday, December 29, 2021 Exempted
Spring Tool Suite 3.9.6 19751 Sunday, September 23, 2018 Approved
Spring Tool Suite 3.9.5 3382 Monday, July 16, 2018 Approved
STS (Install) 3.7.3 2207 Thursday, March 31, 2016 Approved
Discussion for the STS (Install) Package

Ground Rules:

  • This discussion is only about STS (Install) and the STS (Install) 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 STS (Install), 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