Brandon P. Becker wrote:
| A security patch was recently installed to fix a problem with Java
| applets, I believe.
|
| Since that patch, the behavior of Java has changed dramatically and
to
| the point of no longer being usable.
Bob Lang wrote:
| I wonder if this might be a Terminal problem?
Unlikely. Terminal would have to be selectively discarding user input
to
explain
| 1. javac abc.java no longer initiates a compile of
abc.java.
| Instead a multi line diag is issued starting with:
| javac: no source files
| Usage: javac <options> <source files>
| where possible options include:
where the "javac" command appears to ignore its first argument.
Terminal is,
as its name says, merely a *terminal*. It simply relays text back and
forth
to the shell and programs started from the shell. For Terminal to be
able to
cause this symptom, it would have to understand what's being typed.
Nor would weird Terminal settings explain
| Changing the compile line to
| javac -verbose abc.java
| will initiate the compile, but only if abc is self-contained, the
| compiler fails to find class files in the directory where the file
| abc.java = the directory where the compile was initiated. An
example
| is appended to this email.
Scrambled *shell* settings might be able to do that, since the shell
manages
environment variables, which *do* affect Java. (But even they wouldn't
cause
"javac" to ignore arguments.)
The symptoms suggest a broken Java installation.
I think my first guess would be to delete the most recent Java-update
receipt, then reinstall that update.
Glen Fisher
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/
email@hidden
This email sent to email@hidden
