I updated to OS X 10.9 mavericks. It seems this update removed Java 1.6. That’s fine with me. I have Jave 1.7 from oracle installed.
But now every time I open jitsi, I get the notice to install java 1.6. Is 1.6 still a requirement for jitsi to work? Isn’t it possible to use the existing java 1.7 on my machine?
Can someone elaborate on this? Think, updating jitsi, to use the latest java might be a smart idea?
We already ship Jitsi with Java 1.7 on Windows so there is nothing to
update there.
There seems however that there is indeed a problem with hour Mavericks
handles the absence of Java. (Apple seem to have gradually worsened
the experience of Java's installation during the last versions).
We should look into this but the options are basically the following:
a) we find a way to make Mavericks download and install a Java version
for us (and to only ask once and not on every start as in your case)
b) we ship with the JRE we want
I think option b) might be more appropriate since it would also allow
us to enter the app store.
I updated to OS X 10.9 mavericks. It seems this update removed Java 1.6. That’s fine with me. I have Jave 1.7 from oracle installed.
But now every time I open jitsi, I get the notice to install java 1.6. Is 1.6 still a requirement for jitsi to work? Isn’t it possible to use the existing java 1.7 on my machine?
Can someone elaborate on this? Think, updating jitsi, to use the latest java might be a smart idea?
We already ship Jitsi with Java 1.7 on Windows so there is nothing to
update there.
There seems however that there is indeed a problem with hour Mavericks
handles the absence of Java. (Apple seem to have gradually worsened
the experience of Java's installation during the last versions).
Well, Apple wants to move people towards the new Java 1.7. Per se that seems to be a good idea.
We should look into this but the options are basically the following:
a) we find a way to make Mavericks download and install a Java version
for us (and to only ask once and not on every start as in your case)
Well if I download Java 1.6 jitsi will no longer ask. But as I said, I’d like to use Java 1.7.
b) we ship with the JRE we want
I think option b) might be more appropriate since it would also allow
us to enter the app store.
So I’m not sure yet, should Jitsi work with Java 1.7 on OS X?
The source itself work with 1.7 yes. The current packaging may
indicate a preference for 1.6 (if that's the case it is simply a
leftover and not an actual requirement) so it may not work with 1.7
Option b), which we will work on next week, would come with J1.7
pre-packaged in the Jitsi dmg, so there won't be any need for anyone
to download any version of Java.
Well if I download Java 1.6 jitsi will no longer ask. But as I said, I’d like to use Java 1.7.
b) we ship with the JRE we want
I think option b) might be more appropriate since it would also allow
us to enter the app store.
So I’m not sure yet, should Jitsi work with Java 1.7 on OS X?
The source itself work with 1.7 yes. The current packaging may
indicate a preference for 1.6 (if that's the case it is simply a
leftover and not an actual requirement) so it may not work with 1.7
Option b), which we will work on next week, would come with J1.7
pre-packaged in the Jitsi dmg, so there won't be any need for anyone
to download any version of Java.
Well if I download Java 1.6 jitsi will no longer ask. But as I said, I’d like to use Java 1.7.
b) we ship with the JRE we want
I think option b) might be more appropriate since it would also allow
us to enter the app store.
So I’m not sure yet, should Jitsi work with Java 1.7 on OS X?
The source itself work with 1.7 yes. The current packaging may
indicate a preference for 1.6 (if that's the case it is simply a
leftover and not an actual requirement) so it may not work with 1.7
Option b), which we will work on next week, would come with J1.7
pre-packaged in the Jitsi dmg, so there won't be any need for anyone
to download any version of Java.
> On Fri, Oct 25, 2013 at 4:24 PM, Steve <stevebell@gulli.com> wrote:
>> Well if I download Java 1.6 jitsi will no longer ask. But as I said,
I’d like to use Java 1.7.
>>
>>> b) we ship with the JRE we want
>>>
>>> I think option b) might be more appropriate since it would also allow
>>> us to enter the app store.
>>
>> So I’m not sure yet, should Jitsi work with Java 1.7 on OS X?
>
> The source itself work with 1.7 yes. The current packaging may
> indicate a preference for 1.6 (if that's the case it is simply a
> leftover and not an actual requirement) so it may not work with 1.7
>
> Option b), which we will work on next week, would come with J1.7
> pre-packaged in the Jitsi dmg, so there won't be any need for anyone
> to download any version of Java.
>
> Hope this answers your question,
> Emil
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
Thanks for the quick report.
We tried upgrading to embed jre in dmg but there is a problem with
code signing the new launcher on the build machine. So we reverted it,
only a agent lib renaming was left which is your problem and is now
fixed in latest nightly.
Well if I download Java 1.6 jitsi will no longer ask. But as I said, I’d like to use Java 1.7.
b) we ship with the JRE we want
I think option b) might be more appropriate since it would also allow
us to enter the app store.
So I’m not sure yet, should Jitsi work with Java 1.7 on OS X?
The source itself work with 1.7 yes. The current packaging may
indicate a preference for 1.6 (if that's the case it is simply a
leftover and not an actual requirement) so it may not work with 1.7
Option b), which we will work on next week, would come with J1.7
pre-packaged in the Jitsi dmg, so there won't be any need for anyone
to download any version of Java.