Downloads:

106,293

Downloads of v 4.4.1:

665

Last Update:

03 Dec 2014

Package Maintainer(s):

Thilas

Software Author(s):

Eclipse Foundation

Tags:

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

Eclipse

This is not the latest version of Eclipse available.

4.4.1 | Updated: 03 Dec 2014

Downloads:

106,293

Downloads of v 4.4.1:

665

Maintainer(s):

Thilas

Software Author(s):

Eclipse Foundation

Tags:

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

Eclipse 4.4.1

This is not the latest version of Eclipse available.

All Checks are Unknown

2 Test of Unknown Status

Hide Checks

Validation Testing Unknown

Verification Testing Unknown

Individual
Organization

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:

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

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://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

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the Package Download
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run choco download eclipse --internalize --version=4.4.1 --source=https://chocolatey.org/api/v2 (additional options)
- Run choco push --source="'http://internal/odata/repo'" for package and dependencies
- Automate package internalization

3. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade eclipse -y --source="'STEP 3 URL'" [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="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Ensure eclipse installed
  win_chocolatey:
    name: eclipse
    state: present
    version: 4.4.1
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'eclipse' do
  action    :install
  version  '4.4.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: eclipse,
    Version: 4.4.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller eclipse
{
   Name     = 'eclipse'
   Ensure   = 'Present'
   Version  = '4.4.1'
   Source   = 'STEP 3 URL'
}

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


package { 'eclipse':
  provider => 'chocolatey',
  ensure   => '4.4.1',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install eclipse version="4.4.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. 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.

Description

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 - https://github.com/030/chocolateyautomatic/issues

Files

tools\chocolateyInstall.ps1

$packageName = 'eclipse'
$packageVersion = '4.4.1'
$32BitUrl = 'http://eclipse.mirror.triple-it.nl/technology/epp/downloads/release/luna/SR1/eclipse-jee-luna-SR1-win32.zip'
$64BitUrl = 'http://eclipse.mirror.triple-it.nl/technology/epp/downloads/release/luna/SR1/eclipse-jee-luna-SR1-win32-x86_64.zip'
$global:installLocation = "C:\Program Files\Eclipse Foundation\$packageVersion"

. "$PSScriptRoot\OverwriteParameters030.ps1"

OverwriteParameters030

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

tools\chocolateyUninstall.ps1

$packageName = 'eclipse'

. "$PSScriptRoot\Uninstall-ChocolateyZipPackage030.ps1"

Uninstall-ChocolateyZipPackage030 "$packageName"

tools\OverwriteParameters030.ps1

function OverwriteParameters030 {
	$arguments = @{};
	$packageParameters = $env:chocolateyPackageParameters;

	if($packageParameters) {
		$MATCH_PATTERN = "/([a-zA-Z]+)=([`"'])?(.*)([`"'])?"
		$PARAMATER_NAME_INDEX = 1
		$VALUE_INDEX = 3
		
		if($packageParameters -match $MATCH_PATTERN){
			$results = $packageParameters | Select-String $MATCH_PATTERN -AllMatches 
			$results.matches | % { 
			$arguments.Add(
				$_.Groups[$PARAMATER_NAME_INDEX].Value.Trim(),
				$_.Groups[$VALUE_INDEX].Value.Trim()) 
			}
		}     
		
		if($arguments.ContainsKey("InstallLocation")) {
			$global:installLocation = $arguments["InstallLocation"];
			Write-Host "Value variable installLocation changed to $global:installLocation"
		}
	}	
}

tools\Uninstall-ChocolateyZipPackage030.ps1

function Uninstall-ChocolateyZipPackage030 {
param(
  [string] $packageName
)
	ChildItem "$env:ChocolateyInstall\lib\${packageName}.*" -Recurse -Filter "${packageName}Install.zip.txt" | 
	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}}
}

Virus Scan Results

eclipse.4.4.1.nupkg (8258e0ff8df1) - ## / 56 - 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.

Version History

Version	Downloads	Last Updated	Status
Eclipse 4.13	10315	Wednesday, September 18, 2019	Approved
Eclipse 4.12	11592	Sunday, June 23, 2019	Approved
Eclipse 4.11	773	Thursday, June 20, 2019	Approved
Eclipse 4.10	14655	Tuesday, December 25, 2018	Approved
Eclipse 4.9.0.20181212	1715	Wednesday, December 12, 2018	Approved
Eclipse 4.9	3122	Wednesday, November 21, 2018	Approved
Eclipse 4.8.0	9409	Thursday, June 28, 2018	Approved
Eclipse 4.7.3.1	133	Thursday, July 26, 2018	Approved
Eclipse 4.7.3	6056	Wednesday, March 21, 2018	Approved
Eclipse 4.7.2	5504	Wednesday, December 20, 2017	Approved
Eclipse 4.7.1.20171220	417	Wednesday, December 20, 2017	Approved
Eclipse 4.7.1.20171009	4935	Saturday, October 21, 2017	Approved
Eclipse 4.7.1	1991	Thursday, September 28, 2017	Approved
Eclipse 4.7	7275	Saturday, July 15, 2017	Approved
Eclipse 4.6.3	268	Saturday, July 15, 2017	Approved
Eclipse 4.5.2	224	Saturday, July 15, 2017	Approved
Eclipse 4.5.1	17033	Saturday, October 3, 2015	Approved
Eclipse 4.5	2987	Sunday, June 28, 2015	Approved
Eclipse 4.4.2	1533	Monday, April 13, 2015	Approved
Eclipse 4.4.1.20150117	1534	Sunday, January 18, 2015	Approved
Eclipse 4.4.1.20150103	774	Saturday, January 3, 2015	Approved
Eclipse 4.4.1.20150102	325	Friday, January 2, 2015	Approved
Eclipse 4.4.1	665	Wednesday, December 3, 2014	Approved

Release Notes

http://www.eclipse.org

Dependencies

- jdk8

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.