Downloads of v 4.4.1:


Last Update:

03 Dec 2014

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.4.1 | Updated: 03 Dec 2014



Downloads of v 4.4.1:



Software Author(s):

  • Eclipse Foundation

  • 1
  • 2
  • 3
Eclipse 4.4.1

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 Unknown

Verification Testing Unknown

Scan Testing Resulted in Investigate


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.4.1'" [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.4.1'" 

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.4.1'
    state: present

See docs at

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

See docs at

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

Requires cChoco DSC Resource. See docs at

package { 'eclipse':
  ensure   => '4.4.1',
  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 ferventcoder on 04 Dec 2014.


Eclipse IDE facilitates programming. One could develop Java code by creating it, compile it using javac and run it. Eclipse is able to validate code during development. E.g. if code cannot be compiled Eclipse will highlight the code that causes the issue. Eclipse supports native and custom shortcuts that could accelerate development.

Suitable for developers of other languages than Java as well:

Although the Eclipse Foundation highlights that this package has been designed for Java EE Developers as it is called Eclipse IDE for Java EE Developers. Developers of other languages could use this package as well by installing additional software. E.g. Python, Ruby, Groovy, Go, Clojure, Haskell, Scala developers could use Eclipse as an IDE as well. In addition to programming, it is possible to create statistical reports by installing BIRT.

Optional installation commands:

Issue -packageparameters '"/InstallLocation=C:\Path\to\installationdirectory"' to overwrite the default installation directory, e.g. choco install eclipse -packageparameters '"/InstallLocation=C:\temp"' extracts the package in C:\temp.

Bugs and Features:

Create an issue or comment to an existing one -

$packageName = 'eclipse'
$packageVersion = '4.4.1'
$32BitUrl = ''
$64BitUrl = ''
$global:installLocation = "C:\Program Files\Eclipse Foundation\$packageVersion"

. "$PSScriptRoot\OverwriteParameters030.ps1"


Install-ChocolateyZipPackage "$packageName" "$32BitUrl" "$global:installLocation" "$64BitUrl"
$packageName = 'eclipse'

. "$PSScriptRoot\Uninstall-ChocolateyZipPackage030.ps1"

Uninstall-ChocolateyZipPackage030 "$packageName"
function OverwriteParameters030 {
	$arguments = @{};
	$packageParameters = $env:chocolateyPackageParameters;

	if($packageParameters) {
		$MATCH_PATTERN = "/([a-zA-Z]+)=([`"'])?(.*)([`"'])?"
		if($packageParameters -match $MATCH_PATTERN){
			$results = $packageParameters | Select-String $MATCH_PATTERN -AllMatches 
			$results.matches | % { 
		if($arguments.ContainsKey("InstallLocation")) {
			$global:installLocation = $arguments["InstallLocation"];
			Write-Host "Value variable installLocation changed to $global:installLocation"
function Uninstall-ChocolateyZipPackage030 {
  [string] $packageName
	ChildItem "$env:ChocolateyInstall\lib\${packageName}.*" -Recurse -Filter "${packageName}" | 
	ForEach-Object{ $extractionPath = (Get-Content $_.FullName | Select-Object -First 1); Write-Host "Uninstalling by removing directory $extractionPath"; if (($extractionPath -match "${packageName}") -and (Test-Path -Path $extractionPath)){Remove-Item -Recurse -Force $extractionPath}}

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 10075 Thursday, December 17, 2020 Approved
Eclipse 4.17 10202 Wednesday, September 16, 2020 Approved
Eclipse 4.16 43430 Wednesday, June 17, 2020 Approved
Eclipse 4.15 29347 Thursday, March 19, 2020 Approved
Eclipse 4.14 24564 Sunday, December 22, 2019 Approved
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