Dr Java Mac Download Java Jar File Could Not Be Launched

 



Java JAR-file could not be launched, Mac. Ask Question Asked 6 years ago. Active 6 years ago. Viewed 6k times -1. I'm simply trying to open a JAR file on my Mac. I'm having a similar problem. I launch the.jar and it says 'The Java JAR file'Voltz.jar' could not be launched.' Then I try the launch.sh and it says 'unable to access jar file Voltz.jar'. I can't figure out how to fix it. I'm on Mac OS X 10.9 and I'm using a 1.5.2 Forge Server. In the dialog that appears select Java- JAR file- Next. Put the package under the directory. Eoj bin Release etcoreapp1.1 win10-x64 publish Create another project, and import org.neo.smartcontract.framework.jar we got in last step. Create a class, e.g. Go.java, and paste the following code into the class file. To obtain DrJava apps for Windows and Mac OS X corresponding to this jar file, see www.drjava.org. Update: this version in fact is not compatible with Java 8. It still checks for a feature in the tools.jar file that is present in Java 7 but not in Java 7.

This page describes how to install and uninstall JDK 8 for OS X computers.

This page has these topics:

See 'JDK 8 and JRE 8 Installation Start Here' for general information about installing JDK 8 and JRE 8.

See 'OS X Platform Install FAQ' for general information about installing JDK 8 on OS X.

System Requirements

Observe the following requirements:

Mac

  • Any Intel-based computer running OS X 10.8 (Mountain Lion) or later.

  • Administrator privileges.

Note that installing the JDK on OS X is performed on a system wide basis, for all users, and administrator privileges are required. You cannot install Java for a single user.

Installing the JDK also installs the JRE. The one exception is that the system will not replace the current JRE with a lower version. To install a lower version of the JRE, first uninstall the current version as described in 'Uninstalling the JRE'.

JDK Installation Instructions

When you install the Java Development Kit (JDK), the associated Java Runtime Environment (JRE) is installed at the same time. The JavaFX SDK and Runtime are also installed and integrated into the standard JDK directory structure.

Depending on your processor, the downloaded file has one of the following names:

  • jdk-8uversion-macosx-amd64.dmg

  • jdk-8uversion-macosx-x64.dmg

Where version is 6 or later.

  1. Download the file.

    Before the file can be downloaded, you must accept the license agreement.

  2. From either the Downloads window of the browser, or from the file browser, double click the .dmg file to launch it.

    A Finder window appears containing an icon of an open box and the name of the .pkg file.

  3. Double click the package icon to launch the Install app.

    The Install app displays the Introduction window.


    Note:

    In some cases, a Destination Select window appears. This is a bug, as there is only one option available. If you see this window, select Install for all users of this computer to enable the Continue button.

  4. Click Continue.

    The Installation Type window appears.

  5. Click Install.

    A window appears that says 'Installer is trying to install new software. Type your password to allow this.'

  6. Enter the Administrator login and password and click Install Software.

    The software is installed and a confirmation window appears.

  7. Refer to http://www.oracle.com/technetwork/java/javase/downloads/jdk-for-mac-readme-1564562.html for more information about the installation.

  8. After the software is installed, delete the .dmg file if you want to save disk space.

Determining the Default Version of the JDK

Dr Java Mac Download Java Jar File Could Not Be Launched Completely

If you have not yet installed Apple's Java OS X 2012-006 update, then you are still using a version of Apple Java 6 that includes the plug-in and the Java Preferences app. See 'Note for Users of OS X that Include Apple Java 6 Plug-in'.

There can be multiple JDKs installed on a system, as many as you wish.

When launching a Java application through the command line, the system uses the default JDK. It is possible for the version of the JRE to be different than the version of the JDK.

You can determine which version of the JDK is the default by typing java -version in a Terminal window. If the installed version is 8u6, you will see a string that includes the text 1.8.0_06. For example:

To run a different version of Java, either specify the full path, or use the java_home tool:

For more information, see the java_home(1) man page.

Uninstalling the JDK

To uninstall the JDK, you must have Administrator privileges and execute the remove command either as root or by using the sudo(8) tool.

For example, to uninstall 8u6:

Do not attempt to uninstall Java by removing the Java tools from /usr/bin. This directory is part of the system software and any changes will be reset by Apple the next time you perform an update of the OS.

Java™ SE Development Kit 7, Update 40 (JDK 7u40)

The full version string for this update release is 1.7.0_40-b43 (where 'b' means 'build'). The version number is 7u40.

Highlights

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

Olson Data 2013d

JDK 7u40 contains Olson time zone data version 2013d. For more information, refer to Timezone Data Versions in the JRE Software.

Security Baselines

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

JRE Family VersionJRE Security Baseline (Full Version String)
71.7.0_25
61.6.0_51
5.01.5.0_51

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 7u40 is 12/10/2013. After this date, Java will provide additional warnings and reminders to users to update to the newer version. For more information, see JRE Expiration Date.

Java Mission Control (JMC) 5.2 Release Notes

Java Mission Control (JMC) is a commercial feature available for java users with a commercial License.

JDK 7u40 includes the first release of Java Mission Control (JMC) that is bundled with the Hotspot JVM. For more information, see JMC Release Notes.

JavaFX Release Notes

JavaFX is now part of JDK. JDK 7u40 release includes JavaFX version 2.2.40.

For a list of bug fixes included this release, see JavaFX Bug Fixes page.

For a list of known JavaFX issues, see Known Issues.

JDK for Linux ARM

Serviceability Agent support: Serviceability Agent (SA) is now supported in JDK for ARM.

ARM hard float support: 7u40 adds ARM Hard-Float ABI (ARMHF) support in addition to existing ARM Soft-Float ABI support. The ARMHF bundle is labeled arm-vfp-hflt.

A target system must provide access to ld-linux-armhf.so.3 dynamic linker/loader through a hard or symbolic link.

Note: The Server JIT compiler (C2) requires ARMv7.

New Features and Changes


Retina Display support on Mac OS X

Retina screens will now display content correctly. Previously rendering had been blurry. See 8000629.

Deployment Rule Set

Deployment rule set allows a desktop administrator to control the level of Java client compatibility and default prompts across an organization.

For a summary of this feature, see Deployment Rule Set documentation.

Option to disable the 'JRE out of date' warning

Starting from 7u40, a new deployment property deployment.expiration.check.enabled is available. This property can be used to disable the 'JRE out of date' warning.

When the installed JRE (7u10 or later), falls below the security baseline or passes it's built-in expiration date, an additional warning is shown to users to update their installed JRE to the latest version. For businesses that manage the update process centrally, users attempting to update their JRE individually, may cause problems.

To suppress this specific warning message, add the following entry in the deployment properties file:

deployment.expiration.check.enabled=false

For more information, see Deployment Configuration File and Properties.

New Security Warnings for Unsigned and Self-Signed Applications

New warnings are added in the dialogs for Unsigned and Self-Signed applications.

From the dialogs for Unsigned and Self-Signed applets, 'Remember this decision' option has been removed. In addition, the previously remembered decisions for self-signed and unsigned applets will be ignored.

For more information, see Security Dialogs.

Local Applets return NULL for DocumentBase

Beginning with JDK 7u40, an applet's getDocumentBase() method will return NULL when the applet is running from the local file system.

If applet needs to load resource, here are the options:

  • If the resource is in the applet's JAR(s), the user should be able to load it with class ClassLoader getResoruceAsStream directly, without needing the codebase information.
  • If the resource is in an arbitrary location, which is not inside the applet's JAR(s), the user must have other ways to get to that location, since it is not part of the applet resource. For example, the user.home java system property, provided their applet has all-permissions.

JAXP Security Improvements

JDK 7u40 release contains Java API for XML Processing (JAXP) 1.5, which adds the ability to restrict the set of network protocols that may be used to fetch external resources. For more information, see JEP 185: JAXP 1.5: Restrict Fetching of External Resources.

Default x.509 Certificates Have Longer Key Length

Starting from 7u40, the use of x.509 certificates with RSA keys less than 1024 bits in length is restricted. This restriction is applied via the Java Security property, jdk.certpath.disabledAlgorithms. The default value of jdk.certpath.disabledAlgorithms is now as follows:

jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024

In order to avoid the compatibility issue, users who use X.509 certificates with RSA keys less than 1024 bits, are recommended to update their certificates with stronger keys. As a workaround, at their own risk, users can adjust the key size to permit smaller key sizes through the security property jdk.certpath.disabledAlgorithms.

For more information, see Java PKI Programmer's Guide or JSSE Reference Guide.

Java Start Menu (for Windows)

Starting with JDK 7u40 release, Java menu items are added to the Windows Start Menu to provide easy access to Java resources.

During JRE install, a Java folder is created in the Windows Start Menu, which contains the following items:

  • About Java: opens an About Java window that shows the latest JRE version installed on the system.
  • Check for Updates: opens the Java Control Panel with focus on the Update tab.
  • Configure Java: opens the Java Control Panel with focus on the General tab.
  • Get Help: opens the URL http://java.com/en/download/help/index.xml.
  • Visit Java.com: opens the URL http://java.com/en/.

During JDK install, a Java Development Kit folder is created in the Windows Start Menu, which contains the following items:

  • Reference Documentation: opens the Online API documentation web page.
  • Java Mission Control: opens the Java Mission Control profiling and diagnostics tools suite.

During JRE and/or JDK install and uninstall processes, the appropriate start menu items are updated to be associated with the latest JRE and/or JDK version on the system.

Note: Java Mission Control is a commercial feature available to users with a Java SE Advanced license.

Bug Fixes

For a list of bug fixes included in this release, see JDK 7u40 Bug Fixes page.

The following are some of the known issues in JDK 7u40.

Dr Java Mac Download Java Jar File Could Not Be Launched Called

Area: deploy/plugin

Synopsis: Aborting the update after clicking 'Update' on the 'Java is insecure' warning message forwards all applets to java.com/download.

When an older JRE is installed on the system, launching a web page with an applet prompts the user with 'Java is insecure' message. If the user clicks on the 'Update' button on the message but later aborts the update process, user is automatically redirected to http://java.com/download page.

This is not the expected behavior. The issue is fixed in JDK 7u40 release.

Area: deploy/plugin

Synopsis: Expired (but otherwise valid) certificate are not blocked at VeryHigh Security Level.

Dr Java Mac Download Java Jar File Could Not Be Launched Mac

The issue is fixed in JDK 7u40 release.

Known Issues

The following are some of the notable bug fixes in JDK 7u40 release:

Installer

Area: install/auto_update

Synopsis: On Mac OS X update from the Java Control Panel on a system with JRE 7u25 fails to find JRE 7u40.

Mac OS X users with JRE version 7u25 installed that try to update using the Java Control Panel are told that they have the current version installed rather than being offered the option to install 7u40.

For more details see: JDK-8024640.

Workaround: Manually download JRE 7u40 for Mac OS X from java.com or OTN and install it.

JDK

Area: client/plugin

Synopsis: Locking behavior for JCP is not clear for OCSP/CRL (Adding deployment.security.validation.crl.locked property in config file does not reflect in JCP. )

Adding deployment.security.validation.crl.locked in config file does not seem to disable (gray out) Revocation Check property in Java Control Panel (JCP).

For example, a deployment property file c:WindowsSunJavaDeploymentdeployment.config file is created with the following content:

When the JCP is displayed, the mix code section will be disabled (all grayed out), but the certificate revocation section still active/changeable.

Workaround: The regression is only in display and the locking is working.

Area: client-libs/java.awt

Synopsis: java/awt/Frame/HugeFrame/HugeFrame.java sometimes fails on Mac OS X.

Creating huge frames in Mac OS X on some hardware does not work. The issue is known to be reproducible with Intel HD 4000 video card for frames with more than 10000 pixel size. There is no known workaround.

Area: hotspot/gc

Synopsis: New minimum young generation size is not properly checked by the JVM.

In JDK 7u40, the minimum size of the young generation for the parallel garbage collector was increased from 192 KB to 768 KB in a 32-bit JVM, and to 1536 KB in a 64-bit JVM. This new minimum size is not properly checked by the JVM. If a young generation size that is smaller than the new minimum is specified on the command line, it can result in either a crash or degraded performance.

The young generation size is set by the options -XX:NewSize=<N> and -XX:MaxNewSize=<N>, or by the option -Xmn<N> (the latter option is equivalent to setting both NewSize and MaxNewSize to <N>). If the above options are not used, then the young generation size is computed as a fraction of the maximum heap size.

Workaround: Use a young generation size that is at least 768 KB (for 32-bit JVM) or 1536 KB (for 64-bit JVM).

Area: hotspot/compiler

Synopsis: Irregular crash or corrupt term vectors in the Lucene libraries.

The JVM can crash or produce a corrupt term vector in a narrow corner case in the Lucene library; these types of crashes are caused by a corrupted array index value which sometimes is not initialized properly. The effect of this is an array index value that points to an incorrect element of the array.

For more details see: JDK-8024830.

Workaround: Use the flag -XX:- UseSuperWord at the JVM command line.

Area: hotspot/runtime

Synopsis: Java causes MacOSX to crash with kernel panic

The JVM could cause kernel panic on MacOSX v10.8.1 and v10.8.2. It is an MacOSX issue which is not reproduced on v10.8.3. User needs to upgrade to the latest MacOSX 10.8.x version to avoid this issue.

Area: deploy/plugin

Synopsis: Local applet could not be launched with Firefox 23

Dr Java Mac Download Java Jar File Could Not Be Launched

This is a Firefox bug and a fix will be provided in a future release. This regression is introduced due to a fix against issues related to same-origin policy under Firefox. For more details, see https://bugzilla.mozilla.org/show_bug.cgi?id=902375.

Workaround: To work with Firefox 23, under Firefox preferences, set the property 'security.fileuri.strict_origin_policy' to false.

Area: deploy/plugin

Synopsis: Using the family CLSID to trigger loading of an applet does not work with certain JRE family versions

If you use the family CLSID to trigger loading of an applet with a certain JRE family version, the family CLISD will be ignored and the latest JRE version installed on your system is used to load the applet instead. Family CLSID is specific to Internet Explorer.

Workaround: Use the java_version applet parameter or the version attribute of the Java element in JNLP file instead.

Area: deploy/plugin

Synopsis: Certificate-based DRS rule does not work when main JAR file is in nested resource block

The certificate-based Deployment Rule Set rule does not work properly for JNLP applications when the main JNLP file has no JAR files, or all JAR files are in nested resource blocks nested in <java> or <j2se> elements.

Workaround: Reorganize the application to avoid this scenario.

Launched

JavaFX

Area: Packager

Synopsis: Packager for Mac OS generates invalid ICNS icon.

After an application is packaged with the native Mac OS packager, the .app bundle contains an invalid ICNS icon. When developers try to submit this application to Mac App Store, the Application Loader fails with the error reporting about an invalid ICNS icon.

Workaround:

To overcome the issue, perform the following steps:

  • Change dir into generated bundles directory (./dist/bundles). There you can find MyApp.app.
  • Write entitlements for your application. All programs, delivered by Mac App Store, are started within sandbox, so you have to describe needs of your application in some specific format, described on Apple official sites: some template you can find here. Let this file be named MyApp.entitlements.
  • For some packager bug, we had to remake icon in ./dist/bundles/MyApp.app/Resources:
  • Sign your .app:
  • Sign all sub-libraries and jars:
  • Build signed .pkg:

    Don't be confused by different certificated: there must be at least two certificates: Application certificate and Submission/Installer certificates.

Area: Graphics

Synopsis: The WebView component doesn't support HiDPI rendering.

Area: Graphics

Synopsis: The HiDPI support cannot be enabled inside a LoDPI browser.

Area: Graphics

Synopsis: Point and Spot lights of the Lighting effect are not affected by coordinate scaling.

The coordinates of the lighting sources are not adjusted for the coordinate transform of a node and are actually relative to its bounding box, which makes positioning the lights properly for an arbitrary node tricky.