Java 1.7.0_21 Download For Mac

  1. Java 1.7.0_21 Download For Mac Windows 7
  2. Java 1.6.0.21 Download

Already own Minecraft? Download it again for Windows, Mac and Linux. Download server software for Java and Bedrock and play with your friends. Mac OS X Port Project. The goal of this Project is to produce a high-quality, open source version of JDK 7 for the Mac. The final release has the following goals: Pass all appropriate certification tests for Java SE 7; Include a complete, native Cocoa-based UI Toolkit; Provide excellent performance; This Project is sponsored by the Porters.

This page tells you how to download and install Java 8 and Eclipse on Mac OS X, and how to configure Eclipse.

Installing Java 8

  1. Go to the Oracle website. You'll see something like this:

  2. Scroll down until you see a heading beginning 'Java SE 8u65/8u66.' On the right, you'll see a Download button under the JDK header. Click it. The next screen will look like this:

    Click the radio button next to 'Accept License Agreement' and then click on jdk-8u65-macosx-x64.dmg. You'll be asked whether to save the file that is going to be downloaded; click on Save File.

  3. Open your Downloads folder, and double-click on jdk-8u65-macosx-x64.dmg. You'll see this window:

  4. Double-click on the package icon, and follow the instructions to install. When the installation has completed, click on Done. At this point, you may close up the window and drag jdk-8u65-macosx-x64.dmg to the Trash.

Installing Eclipse

  1. If you already have Eclipse installed on your Mac, you need to get rid of it. To do so, first quit Eclipse if you're currently running it. Then, go to your workspace folder (probably in Documents/workspace) and save anything there that you want to keep, because you're about to get rid of this folder. Next, drag the workspace folder to the Trash.

    Go to your Applications folder. One way to get there is, from the Finder, type command-shift-A. You'll a folder named eclipse in there; drag the eclipse folder to the Trash. If you have an Eclipse icon in your dock, remove it from the dock.

  2. Now you're ready to download and install the newest version of Eclipse. Go to this website. You'll see a window like this:

    Scroll down until you see 'Eclipse IDE for Java Developers' and click where it says 64 bit under Mac OS X.

  3. You will see this window:

    Click on the yellow download button. If asked, click on 'Open with Archive Utility (default)' and then click OK. The download might take a few minutes. You should not feel compelled to donate.

  4. After the download completes, folders should automatically expand. If they don't, double-click on the .tar file. When that's done, you should see a folder named eclipse in your Downloads folder. When you open your Downloads folder, if you see Applications under the Favorites on the left side of the window, you should drag the eclipse folder into Applications. If you don't see Applications, then open a new window for Applications (from the Finder, command-shift-A), and drag the eclipse folder into Applications.

  5. Open your Applications folder, and then open the eclipse folder. You'll see an item named Eclipse; if you like, drag its icon into the dock so that you'll be able to launch Eclipse easily.

  6. Launch Eclipse. If you're asked whether you want to open it, of course you do; click Open. You'll see a window like this:

    It will have your user name rather than mine (scot). Select where you want your workspace to be; I recommend the default of your Documents folder. Click the checkbox for using this location as the default, and then click OK.

  7. You'll see a window like this:

    Click on the Workbench arrow in the upper right that I've circled. You shouldn't see this screen again, even if you quit Eclipse and relaunch it.

  8. You'll get an empty workbench like this:

    We won't be using the 'Task List' and 'Connect Mylyn' windows. Click the 'x' on each to close it. Press the mouse on the Window menu item, then choose 'Perspective', and finally choose 'Save Perspective as...'. Enter 'cs10' for the name of this perspective and press return. Your workbench will now look like this:

    You have now installed Eclipse!

Configuring Eclipse

You don't have to configure Eclipse the way I do, but you'll probably avoid some confusion if you do. Here's how.

  1. In the Eclipse menu bar, click on the Eclipse menu and then on 'Preferences...'. You'll see a window with two panes. On the left pane is a list of types of things you can configure.

  2. Click on the triangle to the left of General. Then click on the triangle to the left of Appearance. Then click on 'Colors and Fonts.' You should see a window like this:

  3. In the window in the middle, click on the triangle next to Java. Then double-click on 'Java Editor Text Font':

  4. You'll see this window:

    On the right, where you can select the size, click 12. Then close this window by clicking on the window's close button.

  5. Close up the General preferences by clicking on the triangle to the left of General. Click the triangle next to Java and then click the triangle next to 'Code Style.' Then click Formatter. Here's what you should see:

  6. Click the button that says 'New...'. You'll see a window such as this one:

    You can type in any profile name you like. I used 'CS 10':

    Click OK.

  7. You should see a window like this:

    Change the tab size to 2:

    You'll see that the indentation size automatically changes as well.

  8. Click on 'Blank Lines,' and after 'Between import groups' and 'Before declarations of the same kind,' change the values 1 to 0:

  9. Click on 'Control Statements,' and check the first four boxes as I've done here:

    Click OK.

  10. Now click on triangles to close up Java. Click on the triangle next to Run/Debug, and then click on Console:

  11. Click on the green color sample next to 'Standard In text color.' You'll get a color picker:

  12. Slide the slider on the right down, so that you get a dark green. (You're at Dartmouth. What other color could you possibly want?)

    Close the color picker window by clicking its close button, and click OK again to close the Preferences window.

  13. And you're done!

Java™ SE Development Kit 7, Update 21 (JDK 7u21)

The full version string for this update release is 1.7.0_21-b11 (where 'b' means 'build') except for Mac OS X for which it is 1.7.0_21-b12. The version number is 7u21.

Highlights

Java 1.7.0_21 Download For Mac Windows 7

This update release contains several enhancements and changes including the following:

Olson Data 2012i

JDK 7u21 contains Olson time zone data version 2012i. For more information, refer to Timezone Data Versions in the JRE Software.

Security Baselines

Java 1.7.0_21 Download For Mac

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 7u21 are specified in the following table:

JRE Family VersionJRE Security Baseline (Full Version String)
71.7.0_21
61.6.0_45
5.01.5.0_45
Java 1.7.0 21 download

For more information about security baselines, see Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer.

JRE Expiration Date

The expiration date for JRE 7u21 is 07/18/2013.

Blacklisted Jars and Certificates

Oracle now manages a certificate and jar blacklist repository. This data is updated on client computers daily on the first execution of a Java applet or web start application.

Changes to Java Control Panel's Security Settings

In this release,low and custom settings are removed from the Java Control Panel(JCP)'s Security Slider.

Depending on the security level set in the Java Control Panel and the user's version of the JRE, self-signed or unsigned applications might not be allowed to run. The default setting of High permits all but local applets to run on a secure JRE. If the user is running an insecure JRE, only applications that are signed with a certificate issued by a recognized certificate authority are allowed to run.

Changes to Security Dialogs

As of JDK 7u21, JavaScript code that calls code within a privileged applet is treated as mixed code and warning dialogs are raised if the signed JAR files are not tagged with the Trusted-Library attribute.

The JDK 7u21 release enables users to make more informed decisions before running Rich Internet Applications (RIAs) by prompting users for permissions before an RIA is run. These permission dialogs include information on the certificate used to sign the application, the location of the application, and the level of access that the application requests. For more information, see User Acceptance of RIAs.

Changes to Application Signing

Starting from JDK 7u21, it is recommended that all applications be signed. In addition, it is also possible to restrict signed applications to the security sandbox.

Therefore, the previous use of the term 'unsigned' to mean an application that ran in the security sandbox and 'signed' to mean an application that ran with extended permissions, is no longer meaningful.

The terminology in the Java Tutorial and the Java SE Guides has been changed to use 'sandbox application' for applications that are restricted to the security sandbox, and 'privileged application' for applications that have extended permissions.

Unsigned or self-signed applications may not be supported in future JDK update releases.

For more information on signing applications, see Understanding Signing and Verification. Deploying with Applet Tag describes setting permissions for an applet within the applet tag.

Changes to RMI

From this release, the RMI property java.rmi.server.useCodebaseOnly is set to true by default. In previous releases the default value was false.

This change of default value may cause RMI-based applications to break unexpectedly. The typical symptom is a stack trace that contains a java.rmi.UnmarshalException containing a nested java.lang.ClassNotFoundException.

Java 1.6.0.21 Download

For more information, see RMI Enhancements.

Server JRE

A new Server JRE package, with tools commonly required for server deployments but without the Java plug-in, auto-update or installer found in the regular JRE package, is available starting from this release. The Server JRE is specifically targeted for deploying Java in server environments and is available for 64-bit Solaris, Windows and Linux platforms. For more information on installing this package, see Installation Instructions.

Some of the tools included in the initial release of the Server JRE package, may not be available in future versions of the Server JRE. Please check future release notes for tools availability if you use this package.

JDK for Linux on ARM

JDk 7u21 release includes support for JDK for Linux on ARM. The product offers headful support for ARMv6 and ARMv7.

The following JDK features are not included or supported in this product:

  • Java WebStart
  • Java Plug-In
  • Garbage First (G1) Collector
  • JavaFX SDK or JavaFX Runtime

In addition, some features of the Serviceability Agent are also not available for Linux on ARM platform.

Java support on ARM is specific to the GNOME Desktop Environment version 1:2.30+7.

Changes to Runtime.exec

On Windows platform, the decoding of command strings specified to Runtime.exec(String), Runtime.exec(String,String[]) and Runtime.exec(String,String[],File) methods, has been improved to follow the specification more closely. This may cause problems for applications that are using one or more of these methods with commands that contain spaces in the program name, or are invoking these methods with commands that are not quoted correctly.

For example, Runtime.getRuntime().exec('C:My Programsfoo.exe bar') is an attempt to launch the program 'C:My' with the arguments 'Programsfoo.exe' and 'bar'. This command is likely to fail with an exception to indicate 'C:My' cannot be found.

The example Runtime.getRuntime().exec('C:My Programsfoo.exe' bar') is an attempt to launch the program 'C:My'. This command will fail with an exception to indicate the program has an embedded quote.

Applications that need to launch programs with spaces in the program name should consider using the variants of Runtime.exec that allow the command and arguments to be specified in an array.

Alternatively, the preferred way to create operating systems processes since JDK 5.0 is using java.lang.ProcessBuilder. The ProcessBuilder class has a much more complete API for setting the environment, working directory and redirecting streams for the process.

Auto-download of JRE through JNLP Disabled

Prior to the release of JDK 7u21, the ability to automatically download a JRE through JNLP was disabled at the web server on Windows platform.

If there is a need to download the JRE automatically when an applet or Java Web Start application is run, use the Deployment Toolkit.

Removal of the usePolicy Permission

The permission named usePolicy that enabled system administrators to disable the Java Plug-In's default security prompting behavior is no longer available.

Bug Fixes

This release contains fixes for security vulnerabilities. For more information, see Oracle Java SE Critical Patch Update Advisory.

Known Issues

Area: install/install
Synopsis: Installing SUNWj7rt fails checksum

While installing the Solaris package for JRE, SUNWj7rt, as part of the installation process the user may see some unexpected checksum failures. These errors do not affect the installed JRE in any way.

See 8011175.

Area: install/install
Synopsis: Installing SUNWj7dev to a no-default location fails checksum

While installing the Solaris pacakge for JDK, SUNWj7dev as part of the installation process, especially when the JDK is installed at a non-default location, user may see some unexpected checksum failures. These errors do not affect the installed JDK in any way.

See 8011174.

Java 1.7.0_21 Download For Mac

Area: deploy/deployment_toolkit
Synopsis: Cannot remove trusted sandbox certs via the ControlPanel or trusted certs per location.

With the new sandbox security dialog box changes in JDK 7u21, user can now trust signed sandbox apps, and optionally trust all apps signed by the same certificate from the same URL. However, there is no way to remove the trusted sandbox certificates through the Control Panel, as one can for other trusted certificates.

The workaround is to manually remove the sandbox.certs keystore from the security directory in user's deployment home directory or remove individual entries using keytool.

Area: deploy/plugin
Synopsis: Security popup while closing application

Starting in JDK 7u21, JavaScript code that calls code within a signed applet running with all permissions is treated as mixed code and warning dialogs are raised if the signed JAR files are not tagged with the Trusted-Library=true attribute.

For a signed applet running with all permissions to JavaScript call, no security dialog (with mixed code warning) should pop up. However mixed code warning is being shown in some scenarios.

As a workaround, if the applet jar is running with all-permissions and uses 'Trusted-library:true' attribute as manifest entry, the mixed code warning will not popup.

Area: deploy/plugin
Synopsis: Per-Applet/Global Packages, Java and netscape Keyword support removed

Starting in 7u21, the support for calling from JavaScript to Java via global java, netscape and Packages JavaScript keyword for Firefox/Chrome, and also the per-applet Packages keyword for IE, are all removed.

Area: deploy/deploy
Synopsis: jnlp-applet could not been launched if its jar has been returned with HTTP HEADER Cache-Control: NoStore

Applet/applications could fail to load if response HEADER contains 'Cache-Control : no-store' value.

As a workaround users can either:

  • Disable cache using Java Control Panel if they don't want to cached the application contents.
  • Use header value 'Cache-Control : no-cache' which will force caches (both proxy and browser) to submit the request every time to the origin server for validation before using a cached contents.

Area: deploy/webstart
Synopsis: Javaws can't switch to offline app run mode if app can't be launched online.

The command javaws <jnlp_url> will fail to launch the cached application if system is offline, even if the application JNLP file has <offline-allowed> element specified. As a workaround users can either:

  • Launch Javaws explicitly with javaws -offline <jnlp_url>
  • Launch the cached application via Java Cache Viewer