| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2143409 | 6u1 | Andrey Ozerov | P3 | Resolved | Fixed | b01 |
| JDK-2142573 | 5.0u11 | Mike Belopuhov | P3 | Resolved | Fixed | b01 |
As of JDK 1.5, both java and javac recurse the manifest classpath of a jar on the java classpath. However, rmic compiler does not use the manifest classpath at all. This impacts a number of our customers adversely. We have made necessary internal changes to our product that make extensive use of manifest classpaths. This bug prevents the loading of required classes when using rmic with the altered jars.
- backported by
-
JDK-2142573 rmic does not use manifest classpath
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-6934615 Relative classpaths in jarfile manifests are handled inefficiently by rmic
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
JDK-4212732 javac seems to ignore classpath manifest entries in jar files
-
- Resolved
-
(1 relates to)