JDK-4856549 : provided improved support for executable JARs
  • Type: Enhancement
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-04-30
  • Updated: 2005-09-29
  • Resolved: 2005-09-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6Resolved
Related Reports
Duplicate :  
JDK-6271065 - java.ext.dirs should be expanded
Relates :  
JDK-4459663 - Using executable jars erases CLASSPATH
Description
Many more applications would benefit from being an executable jar file than are currently available today.

However there are some ease-of-development and ease-of-use issues around
executable JARs.

There are proposals for improving the current support, partly by
documenting the current behavior better and partly by extending it.

###@###.### 2003-04-30
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
14-06-2004
EVALUATION Added to Feature Tracker. ###@###.### 2003-04-30 Deferring further investigation until Mustang. ###@###.### 2003-10-21 ###@###.### 2003-11-11 This bug was filed as a placeholder while discussions were going on to see what could be donw to improve the situation. The conclusion from those discussions was that a mechanism for general use similar to the lib/ext solution should be developed. The existing implementation does not scale and even moderate usage of it would have a tragic effect on performance. Resources didn't exist to implement this in Tiger, so it was deferred to Mustang (or later, or never). However, as a temporary expedient, it was decided that the use of absolute classpaths in jar file manifests be documented. (Currently, the work, but are documented as "not supported": only relative URLS are supported".) The potential dangers of absolute paths should also be documented. Except that on windows, the "absolute paths" must be relative to the current drive. ###@###.### 2003-11-11
11-11-2003