Closed Bug 21971 Opened 26 years ago Closed 24 years ago

Mac-only: Tasks > Tools > Java Console does nothing

Categories

(Core Graveyard :: Java: OJI, defect, P3)

Product:
Core Graveyard
Component:
Java: OJI
Platform:
PowerPC
Mac System 8.6
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: nezbo)

References

Details

summary sez it all: going to the Tasks > Tools > Java Console doesn't bring up the java console (nothing happens). tested with today's bits: 1999121609 (mac and win) and 1999121608 (linux). if this isn't implemented, could it be greyed-out in the menu? (so as to avoid potentially confusing users.) thx!
Transferred to the OJI category
Assignee: malini → drapeau
Component: Java FrontEnd → OJI
Changing to OJI category
NOTE: just changed primary QA contact person.(everything else remains the same)
QA Contact: leila.garin → rpallath
There will probably not be time to fix this one for Beta1, but after the JVM is working again with Beta1 on all platforms (except Linux; no OJI-compliant JVM is yet available), we'll get to implementing this.
Status: NEW → ASSIGNED
Target Milestone: M15
*** Bug 22644 has been marked as a duplicate of this bug. ***
Blocks: 27407
For the record, this used to work, but something else changed and now it doesn't. Sound familiar?
Assignee: drapeau → edburns
Status: ASSIGNED → NEW
I tried the 2000022108 build on WinNT and it works just fine for me. We can assume that anyone who tried _made_sure_ that Java was installed with their particular build (for those using opt bits and an installer) ...right?
So for Mac and Linux can we put a . in front of the menu items or gray it out until the functionality is present. I think some on the browser team will have to that, mcafee for Linux and Matt ?? for Mac.
OJI (or presence of JVM) should enable/disable this menu item, we shouldn't have to do platform-specific UI hacks here.
I haven't witnessed this bug yet so hold off doing anything. I agree with Chris though, it should be done dynamically.
After following the below steps, I have determined that I can't reproduce this bug. If you follow the below steps and determine the same, then please reopen. 02 March 00 Here are the steps I took to enable the viewing of applets in mozilla. STEP 8 IS THE MOST IMPORTANT, and UNUSUAL step. 1. Check tinderbox to see that it's green for win32 clobber 2. Checkout SeaMonkey at around 11:30am on 02 March 2000 3. Built Mozilla with MOZ_DEBUG=1 4. Used the WINNT Add/Remove programs feature to remove any JRE and JDK instance I had installed on my machine. Then I rebooted. 5. Used a find command to make sure there were no instances of any of the following files on my C: drive: jpins32.dll npjava*.dll jpishare.dll jaws.jar This step is also intended to catch the case where you have Netscape Navigator 4.x with the Java plugin installed, which I don't. If you do, you must make sure that you don't have the plugin installed. 6. Downloaded the JRE Release Candidate (RC) 1 release by visiting: http://developer.java.sun.com/developer/earlyAccess/j2sdk13/ And choosing the "One large bundle" option under the heading Internationalized version of Java 2 Runtime Environment 7. Ran the installer exe. 8. Unzipped George's zip file on top of the install location, which for me was C:\Program Files\JavaSoft\JRE\1.3 . 9. Copied C:\Program Files\JavaSoft\JRE\1.3\bin\npjava*.* to my mozilla plugins directory, which is: D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\plugins 10. Ran D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\mozilla.exe After doing the profile manager dance, I was able to view applets without java-related crashes.
After following the below steps, I have determined that I can't reproduce this bug. If you follow the below steps and determine the same, then please reopen. 02 March 00 Here are the steps I took to enable the viewing of applets in mozilla. STEP 8 IS THE MOST IMPORTANT, and UNUSUAL step. 1. Check tinderbox to see that it's green for win32 clobber 2. Checkout SeaMonkey at around 11:30am on 02 March 2000 3. Built Mozilla with MOZ_DEBUG=1 4. Used the WINNT Add/Remove programs feature to remove any JRE and JDK instance I had installed on my machine. Then I rebooted. 5. Used a find command to make sure there were no instances of any of the following files on my C: drive: jpins32.dll npjava*.dll jpishare.dll jaws.jar This step is also intended to catch the case where you have Netscape Navigator 4.x with the Java plugin installed, which I don't. If you do, you must make sure that you don't have the plugin installed. 6. Downloaded the JRE Release Candidate (RC) 1 release by visiting: http://developer.java.sun.com/developer/earlyAccess/j2sdk13/ And choosing the "One large bundle" option under the heading Internationalized version of Java 2 Runtime Environment 7. Ran the installer exe. 8. Unzipped George's zip file on top of the install location, which for me was C:\Program Files\JavaSoft\JRE\1.3 . 9. Copied C:\Program Files\JavaSoft\JRE\1.3\bin\npjava*.* to my mozilla plugins directory, which is: D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\plugins 10. Ran D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\mozilla.exe After doing the profile manager dance, I was able to view applets without java-related crashes.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
This is working for windows but not for Mac in the 2000021317. I'm going to reopen this bug.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
*** Bug 8010 has been marked as a duplicate of this bug. ***
Depends on: 31670
Sounds like this is a sad mac-only bug now. :-( It would be nice to have this fixed... but it is not destabilizing M15 (which is frozen now). I'm pushing this bug to M16 to facilitate the M15 branching.
Target Milestone: M15 → M16
Mac bug.
Assignee: edburns → loki-sun
Status: REOPENED → NEW
changing os to mac.
OS: All → Mac System 8.6
this is a dup of 31670 (or if anything 31670 depends on this, not the other way around as listed)... my kingdom for a dup status indicator..ugh
changing 31670 to this blocking it.. changing platform to mac.. jvmmgr in oji never has getConsole invoked from the menu cell action; so something is not hooked up between those two. ugh - another wunderbar design of bugzilla: since someone already put this as depending on 31670 (instead of the opposite which is correct), i can't take the dependency out and put it in the block in one step... lovely... i'll try it in two steps..
No longer depends on: 31670
Hardware: All → Macintosh
step two.. adding it back in as being blocked.
Blocks: 31670
(more notes for future workers) specifically, the nsJVMManager::ShowJavaConsole method never gets messaged on the mac platform.
M16 has been out for a while now, these bugs target milestones need to be updated.
No target milestone: no resources to work on Macintosh bugs right now.
Target Milestone: M16 → ---
summary
Summary: Menu: Tasks > Tools > Java Console does nothing → Mac-only: Tasks > Tools > Java Console does nothing
Re-assigning this bug to myself, as Loki no longer works at Sun. Leaving target milestone as undefined, as there are no resources to work on Macintosh problems.
Assignee: loki-sun → drapeau
Re-assigning to Terry Noyes. Does the Java Console work now? I dunno.
Assignee: drapeau → tnoyes
nope --trying the bring up the java console on mac now crashes mozilla. filed bug 68207 for that.
please see bug #6872, as those proposed fixes appear to also cure the Java Console bugs.
not sure if this is truly dependent, but adding dep on bug 6872 if terry is right.
Depends on: 6872
Status: NEW → ASSIGNED
Hi Terry, what's the status on this?
Status?
Waiting for bug #6872. With those fixes the console comes up and can be used for output, but only then will we be able to see if there are actual Java Console bugs.
The fix for bug #6872 landed yesterday, and I've tested successfully with a yesterday build and a today build. Changing to FIXED.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
Verified with the Netscape 6 2001041908 build.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.