To open you need a Java SE 6 runtime. Why, when I have 1.7 installed?

JimJohnMarks wrote:

So if one has Lion (10.7) rather than SL, the solution described here can't work? SL was the last version to still have a Java preferences in /app/utilities ?

I don't think that's true. I'm running Mavericks and it prompted me to install Java SE 6 for one of my apps. I did have Java Preferences saved off to a external drive at the time, but did not need to use it for the installation to take place. I still have not installed Java SE 7.

I have both SE 6 and 7 installed. I don't know what your reluctance to install it is all about. Reread the thread and make a decision.

MadMacs0,

That's the opposite of what I want to do.

Insofar as I write Java code myself, I want to use a real version of Java, aka 1.7 provided by Oracle, not some hacked up version that Apple no longer actually supports but which the developer community has been slow to replace.

This would be no problem whatsoever except that a particular piece of audio software I have which came as an included plug-in to a major package update I just purchased comes from one such developer who not only has been slow to update their code to run under 1.7, their support department has informed me that as of this time they have absolutely no intension of updating the runtime environment at all, ever.

I would _prefer_ a work around to installing both versions of Java. From what I've read the Apple install of 1.6 makes a number of silent system level changes and I'd just as soon avoid that if I can.

Obviously, baltwo, at that point my priorities of using this plug-in versus avoiding an install I want to avoid becomes a personal decision. I'm not asking thread participants to make the decision I'm trying to clarify whether or not I have any third options. This thread suggested at least two, but I was never able to get clarification from lkrupp about "add the 'Apple version name' in the Java 7 preference pane" so before I abandoned all hope I was hoping to try copying over the utilities preferences.

If the only way to do that is to have an SL copy near to hand, which I don't have, then I guess I'm out of luck -- unless someone knows where to get such a thing "out there somewhere".

JimJohnMarks wrote:

I would _prefer_ a work around to installing both versions of Java. From what I've read the Apple install of 1.6 makes a number of silent system level changes and I'd just as soon avoid that if I can.

Well that's a new one. Seems like a pretty straight forward installation from my point of view. If you have some links I'd be very interested in reading what that's all about. I have a copy of the latest Apple installer and would be happy to check that out for you when I have the time, but I don't have a clue what they might be talking about so don't know what I'd be looking for.

Perhaps I've misunderstood VicT77's comments here: https://discussions.apple.com/thread/4457735

It would appear that VicT77 was dealing with a different issue, trying to completely get rid of Apple's 1.6. It's easy enough to disable Java 1.6, but much more difficult to completely remove all traces.

Part of that problem is that all versions of OS X come with folders and files that are obviously Java related, even OS X 10.9.3 installs these things. baltwo and I have had numerous discussions about this fact, but have never resolved all the reasoning behind this. Much of what is installed are just empty directories and my theory has always been that at least most of the rest is there to intercept calls to Java by Java based apps or web sites and route them to the notices we see on the need to install the Java JRE. Whether there is actually any real Java code capable of doing anything more in conjunction with an app or OS X has yet to be proven, at least to me.

As far as the symlinks, yes there are quite a few. Fourty-two are in /usr/bin/, one in /usr/libexec/ and more in /usr/share/man/man1/ that link back to the aforementioned 1.6.0.jdk/Contents/Home/. I'm guessing that's for compatibility with apps that expect to find Java in the /usr directory.

MadMacs0 wrote:

It would appear that VicT77 was dealing with a different issue, trying to completely get rid of Apple's 1.6. It's easy enough to disable Java 1.6, but much more difficult to completely remove all traces.

But this is precisely my reluctance to install it in the first place. (a) I don't need it, and wouldn't have to install it at all if various developers would get their code updated more promptly (b) once they finally do update their code, then I _really_ won't need it and will want to remove it completely -- which isn't reasonable to do (c) so I'd much rather avoid installing it at all in the first place if there's a work around.

Since copying files over from SL is a closed door for me, I was hoping lkrupp would clarify "add the 'Apple version name' in the Java 7 preference pane", but that doesn't seem to be forthcoming, so I guess I'll have to wait out Cycling 74 and see if they get their act together.

JimJohnMarks wrote:

But this is precisely my reluctance to install it in the first place. (a) I don't need it, and wouldn't have to install it at all if various developers would get their code updated more promptly

But before you said that you do need it now for that one specific developer.

(b) once they finally do update their code, then I _really_ won't need it and will want to remove it completely -- which isn't reasonable to do

Not sure why you want to remove it as there are probably thousands of Mac users out there that have two versions installed and have never had an issue. Even if you did find an issue, disabling Java SE 6 is simple to accomplish. Since you are running Mavericks I suspect you will find that Java is uninstalled with every 10.9.x update or you could easily restore OS X from the Recovery HD, get rid of it and have a nice fresh system, as well.

(c) so I'd much rather avoid installing it at all in the first place if there's a work around.

I'm afraid I'm from Missouri with regard to what lkrupp told us. I can see where it might be possible to trick an app into believing that Java SE 6 was installed, but I don't believe that app will run Java SE 7 or 8 without error.

MadMacs0 wrote:

JimJohnMarks wrote:

But this is precisely my reluctance to install it in the first place. (a) I don't need it, and wouldn't have to install it at all if various developers would get their code updated more promptly

But before you said that you do need it now for that one specific developer.

If I opt to begin using their software, yes. It was included with something else I've been using for years, so I don't have any meaningful need to use it as such. Although it is irksome to indirectly pay for something and get no use out of it because their development team is too lazy to keep up with the times, I'm not above that to avoid having an unnecssarily cluttered system.

I'm sorry that the way I communicate is (apparently) confusing, that's what I've meant to be saying all along and as far as I can tell, is what I've said.

I really couldn't care less about thousands of other Mac users and their experience. This is my system and I like to retain as deep a level of control over it as I can. _My_ experience with systems where that is not the case is that sooner or later they start having problems you can't find the root of and never find real solutions for. The best way I've found to get long life from a system is to keep it as clean as possible. Installing a hacked up, out of date, proprietary version of Java just doesn't fit into that paradigm. I don't consider restoration from a recovery system to be an "easy" solution to much of anything, but that's neither here nor there.

Thanks for the clarification.

JimJohnMarks wrote:

I don't consider restoration from a recovery system to be an "easy" solution to much of anything, but that's neither here nor there.

Actually, I think it may be something to keep in mind. Those of us that have done this have been more than pleasantly surprised at the resullts. It's nothing like it used to be since it doesn't touch any user files or third party apps, so most settings, etc. are completely intact when you finish. Takes maybe an hour to be back to a fresh as new OS.

Hi!

I solved this problem by downloading and installing the development enviroment (JAva SDK) from the Oracle java download site. The Java RE only works as a plugin in the browser.

http://www.oracle.com/technetwork/java/javase/downloads/jdk-7-netbeans-download- 432126.html

Now Wuala opens without the dreaded "You need to install Apples old cruft" dialog.

Regards,

Rabbe

First, I'm glad you got it working for you but...

Rabbe Sandelin wrote:

The Java RE only works as a plugin in the browser.

Isn't true. The Java RE is working perfectly for me with a couple of Java based applications and stand-alone applets. I suspect it's Wuala that is looking in the wrong place for the Java Runtime code that comes with the Java SE 7 JRE.

That actually didn't work for me—it ended up installing Java in a different place than where Charles checked for it. I got it to work by installing Java from the support page here.

This seems to be working for me also, gajeam. Thanks!