Bug 4307 - jar and javakey programs are not working. (intel and sparc tested)
jar and javakey programs are not working. (intel and sparc tested)
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kaffe (Show other bugs)
6.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-02 02:36 EDT by ipaul
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-18 17:24:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description ipaul 1999-08-02 02:36:49 EDT
I wanted to make a signed jar, and I discovered that both
jar and javakey are not working.
Here is the output of the jar and javakey:


[root@paul /tmp]# jar
java.lang.NoClassDefFoundError: sun/tools/jar/Main
        at java.lang.Throwable.<init>(Throwable.java:40)
        at java.lang.Error.<init>(Error.java:21)
        at
java.lang.LinkageError.<init>(LinkageError.java:21)
        at
java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:21)
[root@paul /tmp]# javakey -dl
java.lang.NoClassDefFoundError: sun/security/provider/Main
        at java.lang.Throwable.<init>(Throwable.java:40)
        at java.lang.Error.<init>(Error.java:21)
        at
java.lang.LinkageError.<init>(LinkageError.java:21)
        at
java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:21)
[root@paul /tmp]# javakey
java.lang.NoClassDefFoundError: sun/security/provider/Main
        at java.lang.Throwable.<init>(Throwable.java:40)
        at java.lang.Error.<init>(Error.java:21)
        at
java.lang.LinkageError.<init>(LinkageError.java:21)
        at
java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:21)
Comment 1 Bill Nottingham 1999-08-18 17:24:59 EDT
Again, this will probably not be fixed in Red Hat until it
is fixed in Kaffe proper.

Note You need to log in before you can comment on or make changes to this bug.