Downloads:

106,293

Downloads of v 4.9.0.20181212:

1,715

Last Update:

12 Dec 2018

Package Maintainer(s):

Software Author(s):

  • Eclipse Foundation

Tags:

eclipse foss cross-platform ide jdk8 jee java scala birt python ruby groovy clojure haskell go

Eclipse

This is not the latest version of Eclipse available.

4.9.0.20181212 | Updated: 12 Dec 2018

Downloads:

106,293

Downloads of v 4.9.0.20181212:

1,715

Maintainer(s):

Software Author(s):

  • Eclipse Foundation

Eclipse 4.9.0.20181212

This is not the latest version of Eclipse available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

  • 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

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.9.0.20181212
    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.9.0.20181212'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: eclipse,
    Version: 4.9.0.20181212,
    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.9.0.20181212'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install eclipse version="4.9.0.20181212" 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 as a trusted package on 12 Dec 2018.

Description

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"
  • /Multi-User - Configure Eclipse as a multi-user install

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


tools\chocolateyBeforeModify.ps1
$ErrorActionPreference = 'Stop'

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

$packageVersion = $Env:ChocolateyPackageVersion

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

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

Remove-Item -Path $installationPath -ErrorAction SilentlyContinue -Recurse -Force

$logPath = Join-Path $Env:ChocolateyPackageFolder '*.zip.txt'
Remove-Item -Path $logPath -ErrorAction SilentlyContinue
tools\chocolateyInstall.ps1
$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"

$multiUser = $packageParameters.ContainsKey('Multi-User')

# *** Automatically filled ***
$packageArgs = @{
    packageName    = 'eclipse'
    url            = 'https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-09/R/eclipse-jee-2018-09-win32.zip&r=1'
    url64bit       = 'https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-09/R/eclipse-jee-2018-09-win32-x86_64.zip&r=1'
    unzipLocation  = $installationPath
    checksum       = 'db0bf3764c5055ca92426efb06365f79403082bc75a425f1fa35221aca6be1e6'
    checksumType   = 'sha256'
    checksum64     = '609592bcdd3531960e66255465bd875c200a337942d80288a268cea5e6e99e59'
    checksumType64 = 'sha256'
}
# *** Automatically filled ***

Install-ChocolateyZipPackage @packageArgs

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

$shortcutName = "Eclipse $packageVersion.lnk"
$eclipsePath = Join-Path $installationPath 'eclipse\eclipse.exe'

if ($multiUser) {
    $shortcutPath = Join-Path $([Environment]::GetFolderPath([System.Environment+SpecialFolder]::CommonDesktopDirectory)) $shortcutName
    $targetPath = Join-Path $installationPath 'eclipse.bat'
    $targetContent = @"
@echo off

set ECLIPSEDIR="%LOCALAPPDATA%\Eclipse.$packageVersion"

if not exist %ECLIPSEDIR% (
  mkdir %ECLIPSEDIR%
)

start "Eclipse" "$eclipsePath" -configuration %ECLIPSEDIR%

"@
    Set-Content $targetPath $targetContent -Encoding Ascii -Force
    Install-ChocolateyShortcut -ShortcutFilePath $shortcutPath -TargetPath $targetPath -IconLocation $eclipsePath
} else {
    $shortcutPath = Join-Path $([Environment]::GetFolderPath([System.Environment+SpecialFolder]::CommonPrograms)) $shortcutName
    Install-ChocolateyShortcut -ShortcutFilePath $shortcutPath -TargetPath $eclipsePath -PinToTaskbar
}
tools\chocolateyUninstall.ps1
# Nothing to do here because uninstall is actually done by chocolateyBeforeModify.ps1 in order to handle upgrade properly.
tools\Get-PackageParameters.ps1
<#
.SYNOPSIS
    Parses parameters of the package

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

.OUTPUTS
    [HashTable]
#>
function Get-PackageParameters {
    [CmdletBinding()]
    param(
       [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: https://github.com/chocolatey/chocolatey-coreteampackages/issues/465

        $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 }
    }
    $res
}
tools\Uninstall-ChocolateyShortcut.ps1
<#
.SYNOPSIS
    Remove a shortcut

.DESCRIPTION
    This deletes a shortcut, at the specified location.

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

.INPUTS
    None

.OUTPUTS
    None

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

.EXAMPLE
    >
    # This will remove a shortcut at the location of "C:\test.lnk"
    Uninstall-ChocolateyShortcut -ShortcutFilePath "C:\test.lnk"

.EXAMPLE
    >
    # Removes a notepad shortcut on the root of C:.
    # Shortcut is also unpinned from taskbar.
    Uninstall-ChocolateyShortcut `
    -ShortcutFilePath "C:\notepad.lnk" `
    -UnpinFromTaskbar
#>
function Uninstall-ChocolateyShortcut {
    param(
        [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."
        return
    }

    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)."
    }
}

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 Downloads Last Updated Status
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

This package has no dependencies.

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