Downloads of v 4.5.2:


Last Update:

15 Jul 2017

Package Maintainer(s):

Software Author(s):

  • Eclipse Foundation


eclipse ide jdk8 jee java scala birt python ruby groovy clojure haskell go


This is not the latest version of Eclipse available.

  • 1
  • 2
  • 3

4.5.2 | Updated: 15 Jul 2017



Downloads of v 4.5.2:



Software Author(s):

  • Eclipse Foundation

  • 1
  • 2
  • 3
Eclipse 4.5.2

This is not the latest version of Eclipse available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


Deployment Method: Individual Install, Upgrade, & Uninstall

To install Eclipse, run the following command from the command line or from PowerShell:


To upgrade Eclipse, run the following command from the command line or from PowerShell:


To uninstall Eclipse, 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 eclipse -y --source="'INTERNAL REPO URL'" --version="'4.5.2'" [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 eclipse -y --source="'INTERNAL REPO URL'" --version="'4.5.2'" 

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

Exit $exitCode

- name: Install eclipse
    name: eclipse
    version: '4.5.2'
    state: present

See docs at

chocolatey_package 'eclipse' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.5.2'

See docs at

cChocoPackageInstaller eclipse
    Name     = "eclipse"
    Version  = "4.5.2"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'eclipse':
  ensure   => '4.5.2',
  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.

This package was approved by moderator flcdrg on 22 Jul 2017.


Eclipse is famous for our Java Integrated Development Environment (IDE), but our C/C++ IDE and PHP IDE are pretty cool too. You can easily combine language support and other features into any of our default packages, and the Eclipse Marketplace allows for virtually unlimited customization and extension.

Eclipse IDE for Java EE Developers

Tools for Java developers creating Java EE and Web applications, including a Java IDE, tools for Java EE, JPA, JSF, Mylyn, EGit and others.

This package includes:

  • Data Tools Platform
  • Git integration for Eclipse
  • Eclipse Java Development Tools
  • Eclipse Java EE Developer Tools
  • JavaScript Development Tools
  • Maven Integration for Eclipse
  • Mylyn Task List
  • Eclipse Plug-in Development Environment
  • Remote System Explorer
  • Code Recommenders Tools for Java Developers
  • Eclipse XML Editors and Tools

Package Parameters

The following package parameters can be set:

  • /InstallationPath or /InstallLocation - Where to install the binaries to - defaults to "$Env:ProgramFiles\Eclipse Foundation\$packageVersion"

These parameters can be passed to the installer with the use of --params.
For example: --params "'/InstallationPath=C:\path\to\installation'".

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -Parent $MyInvocation.MyCommand.Definition
. "$toolsDir\Uninstall-ChocolateyShortcut.ps1"

$packageVersion = $Env:ChocolateyPackageVersion

$shortcutPath = Join-Path $([Environment]::GetFolderPath([System.Environment+SpecialFolder]::CommonPrograms)) "Eclipse $packageVersion.lnk"
Uninstall-ChocolateyShortcut $shortcutPath -UnpinFromTaskbar

$logPath = Join-Path $Env:ChocolateyPackageFolder "eclipse.$packageVersion.txt"
$installationPath = Get-Content $logPath
Write-Verbose "Previous Installation Path: $installationPath"

Remove-Item -Path $installationPath -ErrorAction SilentlyContinue -Recurse -Force
$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -Parent $MyInvocation.MyCommand.Definition
. "$toolsDir\Get-PackageParameters.ps1"

$packageVersion = $Env:ChocolateyPackageVersion
$packageParameters = Get-PackageParameters

If ($packageParameters.ContainsKey('InstallationPath')) {
  $installationPath = Join-Path $packageParameters.Item('InstallationPath') $packageVersion
} ElseIf ($packageParameters.ContainsKey('InstallLocation')) {
  $installationPath = Join-Path $packageParameters.Item('InstallLocation') $packageVersion
} Else {
  $forceX86 = If ($Env:ChocolateyForceX86) { Get-ProcessorBits 64 } Else { $false }
  $programFilesPath = If ($forceX86) { ${Env:ProgramFiles(x86)} } Else { $Env:ProgramFiles }
  $installationPath = Join-Path $programFilesPath "Eclipse $packageVersion"
Write-Verbose "Installation Path: $installationPath"

# *** Automatically filled ***
$packageArgs = @{
  packageName    = 'eclipse'
  url            = ''
  url64bit       = ''
  unzipLocation  = $installationPath
  checksum       = 'b2d4bedc3fc2bdb95555cf307902eba1e5569b899268ac59d0d6b27b33b7a6b4'
  checksumType   = 'sha256'
  checksum64     = '01b6b36900fd97071768a170ba2f3db530f086d0b0de9fbb466caa92ed4f2d34'
  checksumType64 = 'sha256'
# *** Automatically filled ***

Install-ChocolateyZipPackage @packageArgs

$logPath = Join-Path $Env:ChocolateyPackageFolder "eclipse.$packageVersion.txt"
Set-Content $logPath $installationPath -Encoding UTF8 -Force

$shortcutPath = Join-Path $([Environment]::GetFolderPath([System.Environment+SpecialFolder]::CommonPrograms)) "Eclipse $packageVersion.lnk"
$targetPath = Join-Path $installationPath 'eclipse\eclipse.exe'
Install-ChocolateyShortcut -ShortcutFilePath $shortcutPath -TargetPath $targetPath -PinToTaskbar
    Parses parameters of the package

    Get-PackageParameters "/Shortcut /InstallDir='C:\Program Files\xyz' /NoStartup" | set r
    if ($r.Shortcut) {... }
    Write-Host $r.InstallDir

function Get-PackageParameters {
       [string] $Parameters = $Env:ChocolateyPackageParameters,
       # Allows splatting with arguments that do not apply and future expansion. Do not use directly.
       [parameter(ValueFromRemainingArguments = $true)]
       [Object[]] $IgnoredArguments

    $res = @{}

    $re = "\/([a-zA-Z0-9]+)(=[`"'].+?[`"']|[^ ]+)?"
    $results = $Parameters | Select-String $re -AllMatches | select -Expand Matches
    foreach ($m in $results) {
        if (!$m) { continue } # must because of posh 2.0 bug:

        $a = $m.Value -split '='
        $opt = $a[0].Substring(1); $val = $a[1..100] -join '='
        if ($val -match '^(".+")|(''.+'')$') {$val = $val -replace '^.|.$'}
        $res[ $opt ] = if ($val) { $val } else { $true }
function Uninstall-ChocolateyShortcut {
Remove a shortcut
This deletes a shortcut, at the specified location.
If this errors, as it may if being run under the local SYSTEM account with
particular folder that SYSTEM doesn't have, it will display a warning instead
of failing a package installation.
.PARAMETER ShortcutFilePath
The full absolute path to where the shortcut is.
.PARAMETER UnpinFromTaskbar
OPTIONAL - Unpin the shortcut from the taskbar.
.PARAMETER IgnoredArguments
Allows splatting with arguments that do not apply. Do not use directly.
# This will remove a shortcut at the location of "C:\test.lnk"
Uninstall-ChocolateyShortcut -ShortcutFilePath "C:\test.lnk"
# Removes a notepad shortcut on the root of C:.
# Shortcut is also unpinned from taskbar.
Uninstall-ChocolateyShortcut `
  -ShortcutFilePath "C:\notepad.lnk" `
    [parameter(Mandatory=$true, Position=0)][string] $shortcutFilePath,
    [parameter(Mandatory=$false)][switch] $UnpinFromTaskbar,
    [parameter(ValueFromRemainingArguments = $true)][Object[]] $ignoredArguments

  Write-FunctionCallLogMessage -Invocation $MyInvocation -Parameters $PSBoundParameters

  if (!$shortcutFilePath) {
    # shortcut file path could be null if someone is trying to get special
    # paths for LocalSystem (SYSTEM).
    Write-Warning "Unable to remove shortcut. `$shortcutFilePath can not be null."

  try {
    if ($UnpinFromTaskbar) {
      if (Test-Path $shortcutFilePath) {$pinverb = (New-Object -com "shell.application").namespace($(split-path -parent $shortcutFilePath)).Parsename($(split-path -leaf $shortcutFilePath)).verbs() | ?{$_.Name -eq 'Unpin from tas&kbar'}}
      if ($pinverb) {$pinverb.doit()}

    Write-Debug "Removing Shortcut..."
    Remove-Item -Path "$shortcutFilePath" -ErrorAction SilentlyContinue -Force
    Write-Debug "Shortcut removed."
  catch {
    Write-Warning "Unable to remove shortcut. Error captured was $($_.Exception.Message)."

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
Eclipse 4.20 21553 Wednesday, June 16, 2021 Approved
Eclipse 4.19 11279 Wednesday, March 17, 2021 Approved
Eclipse 4.18 10074 Thursday, December 17, 2020 Approved
Eclipse 4.17 10200 Wednesday, September 16, 2020 Approved
Eclipse 4.16 43428 Wednesday, June 17, 2020 Approved
Eclipse 4.15 29341 Thursday, March 19, 2020 Approved
Eclipse 4.14 24564 Sunday, December 22, 2019 Approved

    • jdk8 (≥ 8.0.131)
Discussion for the Eclipse Package

Ground Rules:

  • This discussion is only about Eclipse and the Eclipse 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 Eclipse, 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