Downloads:

50,870

Downloads of v 8.0.74:

399

Last Update:

2/12/2016

Package Maintainer(s):

Software Author(s):

  • Oracle

Tags:

java server runtime environment jre admin

Server JRE (Java SE Runtime Environment)

This is not the latest version of Server JRE (Java SE Runtime Environment) available.

8.0.74 | Updated: 2/12/2016

Downloads:

50,870

Downloads of v 8.0.74:

399

Maintainer(s):

Software Author(s):

  • Oracle

Server JRE (Java SE Runtime Environment) 8.0.74

This is not the latest version of Server JRE (Java SE Runtime Environment) available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Server JRE (Java SE Runtime Environment), run the following command from the command line or from PowerShell:

>

To upgrade Server JRE (Java SE Runtime Environment), run the following command from the command line or from PowerShell:

>

To uninstall Server JRE (Java SE Runtime Environment), 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 server-jre8 -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 server-jre8 -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 server-jre8 installed
  win_chocolatey:
    name: server-jre8
    state: present
    version: 8.0.74
    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 'server-jre8' do
  action    :install
  version  '8.0.74'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: server-jre8,
    Version: 8.0.74,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller server-jre8
{
   Name     = 'server-jre8'
   Ensure   = 'Present'
   Version  = '8.0.74'
   Source   = 'STEP 3 URL'
}

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


package { 'server-jre8':
  provider => 'chocolatey',
  ensure   => '8.0.74',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install server-jre8 version="8.0.74" 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 2/12/2016.

Description

Server JRE (Server Java Runtime Environment) for deploying Java applications on servers. Includes tools for JVM monitoring and tools commonly required for server applications, but does not include browser integration (the Java plug-in), auto-update, nor an installer.

Note

This package unpacks the Java Server JRE version offered at https://www.java.com to the default directory "C:\tools\Java\server-jre\jre1.8.0_71".

If you wish to unpack to an alternate directory, use the 'InstallationPath' parameter. Example: choco install server-jre8 -PackageParameters "/InstallationPath:c:\Program Files" -y

The installation will also set the JAVA_HOME environment variable to the destination directory if not present yet and add %JAVA_HOME%/bin to the PATH environment.

This package is only available in 64-bit.

Parameters

  • InstallationPath: Install to a different destination folder. Default: C:\tools\Java\server-jre
  • Force: Force setting JAVA_HOME to the new version even if the variable was already set
  • Machine: Set JAVA_HOME and PATH on 'Machine' level, instead of 'User' level

Install


tools\chocolateyInstall.ps1
$packageName = $env:chocolateyPackageName
$buildNumber = "02"
$checksumMD5 = "48e38e37e0942644922986afd20c4071"

#8.0.71 to jdk1.8.0_74
$versionArray = $env:chocolateyPackageVersion.Split(".")
$majorVersion = $versionArray[0]
$minorVersion = $versionArray[1]
$updateVersion = $versionArray[2]

$folderVersion = "jdk1.$majorVersion.$($minorVersion)_$updateVersion"

$fileNameBase = "server-jre-$($majorVersion)u$($updateVersion)-windows-x64"
$fileName = "$fileNameBase.tar.gz"

$url        = "http://download.oracle.com/otn-pub/java/jdk/$($majorVersion)u$($updateVersion)-b$buildNumber/$fileName"

$osBitness = Get-ProcessorBits
# 32-bit not supported
if ($osBitness -eq 32) {
   Throw "The package $packageName is only available for 64-bit architectures"
}

$arguments = @{}

# Now we can use the $env:chocolateyPackageParameters inside the Chocolatey package
$packageParameters = $env:chocolateyPackageParameters

# Default value
$InstallationPath = Join-Path (Get-BinRoot) "Java/server-jre"
$ForceEnvVars = $false
$EnvVariableType = "User"

# Now parse the packageParameters using good old regular expression
if ($packageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z0-9]+)):(?<value>([`"'])?([a-zA-Z0-9- \(\)\s_\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    $option_name = 'option'
    $value_name = 'value'

    if ($packageParameters -match $match_pattern ){
        $results = $packageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
        $arguments.Add(
            $_.Groups[$option_name].Value.Trim(),
            $_.Groups[$value_name].Value.Trim())
        }
    }
    else
    {
        Throw "Package Parameters were found but were invalid (REGEX Failure)"
    }

    if ($arguments.ContainsKey("InstallationPath")) {
        Write-Host "InstallationPath Argument Found"
        $InstallationPath = $arguments["InstallationPath"]
    }
    if ($arguments.ContainsKey("Force")) {
        Write-Host "Force Argument Found"
        $ForceEnvVars = $true
    }
    if ($arguments.ContainsKey("Machine")) {
        Write-Host "Machine Argument Found"
        $EnvVariableType = "Machine"
    }

} else {
    Write-Debug "No Package Parameters Passed in"
}

Write-Debug "Installing to $InstallationPath, Params: ForceEnvVars=$ForceEnvVars, EnvVariableType=$EnvVariableType"

#Create Temp Folder
$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}

$tarGzFile = "$tempDir\$fileName"
$tarFile = "$tempDir\$fileNameBase.tar"

if ([System.IO.File]::Exists($tarGzFile)) {
    Write-Debug "Checking if existing file $tarGzFile matches checksum"
    #Check sum of existing file
    Try {
        Get-ChecksumValid $tarGzFile $checksumMD5 -ErrorAction Stop
    } 
    Catch{
        Write-Debug "Checksum failed, deleting old file $tarGzFile"
        Remove-Item $tarGzFile
    }
}

if (![System.IO.File]::Exists($tarGzFile)) {
  $wget = Join-Path "$env:ChocolateyInstall" '\bin\wget.exe'
  Write-Debug "wget found at `'$wget`'"

  #Download file. Must set Cookies to accept license
  Write-Debug "Downloading file $tarGzFile"
  .$wget --quiet --no-check-certificate --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" $url -O $tarGzFile
  Get-ChecksumValid $tarGzFile $checksumMD5
}

#Extract gz to .tar File
Get-ChocolateyUnzip $tarGzFile $tempDir
#Extract tar to destination
Get-ChocolateyUnzip $tarFile $InstallationPath

$newJavaHome = Join-Path $InstallationPath $folderVersion
$oldJavaHome = Get-EnvironmentVariable "JAVA_HOME" $EnvVariableType

if(($oldJavaHome -eq $null) -or $ForceEnvVars) {
   Write-Host "Setting JAVA_HOME to $newJavaHome" 
   Install-ChocolateyEnvironmentVariable -variableName "JAVA_HOME" -variableValue $newJavaHome -variableType $EnvVariableType
}
else {
   Write-Debug "JAVA_HOME already set to $oldJavaHome."
}

Install-ChocolateyPath '%JAVA_HOME%\bin' $EnvVariableType

#Remove-Item -Recurse $tempDir
tools\chocolateyUninstall.ps1
$packageName = $env:chocolateyPackageName
#8.0.71 to jdk1.8.0_71
$versionArray = $env:chocolateyPackageVersion.Split(".")
$folderVersion = "jdk1.$($versionArray[0]).$($versionArray[1])_$($versionArray[2])"
$InstallationPath = Join-Path $env:ProgramFiles "Java/server-jre"
$EnvVariableType = "User"

if ([System.IO.Directory]::Exists($InstallationPath)) {
    Write-Debug "Uninstalling $packageName from $InstallationPath"

    $JavaHome = Get-EnvironmentVariable "JAVA_HOME" $EnvVariableType
    if($JavaHome -eq $InstallationPath) {
        Install-ChocolateyEnvironmentVariable -variableName "JAVA_HOME" -variableValue "" -variableType $EnvVariableType
    }
    Remove-Item -Recurse $InstallationPath
}
else {
    Write-Debug "No $packageName found at $InstallationPath"
}

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
Server JRE (Java SE Runtime Environment) 8.0.192 5632 Wednesday, October 17, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.181 6678 Wednesday, July 18, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.172 5193 Wednesday, April 25, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.161 4398 Wednesday, January 24, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.152 4739 Friday, October 20, 2017 Approved
Server JRE (Java SE Runtime Environment) 8.0.144 1907 Sunday, September 24, 2017 Approved
Server JRE (Java SE Runtime Environment) 8.0.131.20170420 6077 Monday, May 1, 2017 Approved

    • wget (≥ 1.17.0.0)
Discussion for the Server JRE (Java SE Runtime Environment) Package

Ground Rules:

  • This discussion is only about Server JRE (Java SE Runtime Environment) and the Server JRE (Java SE Runtime Environment) 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 Server JRE (Java SE Runtime Environment), 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