New Phoenix Core 2.5.8

[stuckless]

The TMDB v3 api relied on a Java 7 api. I've reworked the code so that it no longer depends on Java 7, but come on... Java 6 has been EOLed as of Feb 2013... It's time to move on

So, 2.5.8, just has a small change to TMDB v3 provider and it should work with Java 6 or 7.

[mdnttoker]

Works perfectly, thanks...guess I should finally take the leap to java 7 on the sage server...

[will]

I've been rocking Java 6 for a long time too. Why change what works...

[stuckless]

Originally Posted by will

I've been rocking Java 6 for a long time too. Why change what works...

I understand that on Windows... upgrading Java has been a pain for many people.

Just a word of caution... while I was able to roll out the changes, this time, to make this work in Java 6... There may be other times where I simply won't have the time or will to do so ie, if there's a new feature in Java 7 that makes my life easier as a developer, then I'm going to use it

[tvmaster2]

I've been using Java 7 for a while with my W7 32 bit install...no problems, but I don't use as many plugins as some

[PhilH]

Thanks stuckless. Your work is always appreciated.

Looks like I need to upgrade my Java on my WHS server..

Sorry for the extra work I gave you..

Phil

[routerunner]

Originally Posted by stuckless

I understand that on Windows... upgrading Java has been a pain for many people.

Just a word of caution... while I was able to roll out the changes, this time, to make this work in Java 6... There may be other times where I simply won't have the time or will to do so ie, if there's a new feature in Java 7 that makes my life easier as a developer, then I'm going to use it

Thanks Sean, however if you plan to make any future update that will require upgrading to Java 7, then I kindly ask you to specify the minimum required JVM version in the plugin manifest, this way the user will have, at least, the option to decide whether it is worthwhile make the JVM upgrade without creating any incompatibility issues with the existing setup

Eddy

[stuckless]

Originally Posted by routerunner

Thanks Sean, however if you plan to make any future update that will require upgrading to Java 7, then I kindly ask you to specify the minimum required JVM version in the plugin manifest, this way the user will have, at least, the option to decide whether it is worthwhile make the JVM upgrade without creating any incompatibility issues with the existing setup

Eddy

That's a great idea... I'll add that into the next release. This is important, especially since I wasn't aware that I had used a Java 7 api, I just don't have anything else installed except for Java 7. Next release will include Java 7 manifest entry. (I forgot about that option in the plugin definition)

[sflamm]

FYI - Java 7 works fine with SageTV on all platforms... I am currently running Java 7 update 40 on all of my clients (Win XP, Win 7, Win 8) and my server (Win 2012). No problems whatsoever.

In fact - it is a significant performance improvement over Java 6.... a google search will quickly show the qualitative/measurable details of the performance difference.

[sflamm]

Is this latest update safe? Does it have all the old functionality working or is there something we should make note of?

[stuckless]

Originally Posted by sflamm

Is this latest update safe? Does it have all the old functionality working or is there something we should make note of?

It's as safe as any release... the 2.5.6+ releases was done to address an issue in the movie metadata lookups... and as such it uses a new library for accessing tmdb.

[PhilH]

It works fine here. All of my troubles went away with this release..

[mdnttoker]

Originally Posted by sflamm

Is this latest update safe? Does it have all the old functionality working or is there something we should make note of?

Better than safe, fixed all IMDB and TMDB issues for me...