Jan Haderka wrote:

> On Jan 8, 2013, at 11:45 AM, Nils Breunese <[email protected]> wrote:
> 
>> Jan Haderka wrote:
>> 
>>> On Jan 5, 2013, at 1:59 PM, Nils Breunese <[email protected]> wrote:
>>> 
>>>> http://www.oracle.com/technetwork/java/javase/eol-135779.html mentions 
>>>> that February 2013 marks the end of public updates for Oracle Java SE 6. 
>>>> I'm looking into upgrading all of our infrastructure to Java 7 and on 
>>>> http://documentation.magnolia-cms.com/administration/certified-stack.html 
>>>> I found the following:
>>>> 
>>>> ----
>>>> • Magnolia CMS 4.4 and earlier: Sun JVM 1.5.0 (build 14 and higher), Sun 
>>>> JVM 1.6.x
>>>> • Magnolia CMS 4.5 and later: Java SE 6 or Java SE 7 (except on Mac OS X 
>>>> where you should use Java SE 6)
>>>> ----
>>>> 
>>>> Does this mean Magnolia 4.4 and earlier are not certified to work with 
>>>> Java 7 at all?
>>> 
>>> Yes, 4.4 is not certified. There are issues (from top of my head something 
>>> with comparators, utf-8, and few others) that were fixed only in 4.5.
>> 
>> Ok, thanks for the clarification. And these fixes won't be backported to 4.4?
> 
> Not really planned, no. Long term everyone needs to move to 4.5 or higher 
> version anyway so I prefer to focus on fixing issues there.

I think it would be a bit strange if you kept supporting Magnolia 4.4, but only 
certify it to run it on JVM versions that have reached end of life, but as far 
as I understand that will be the case after February. Fixes the issues with 
running Magnolia 4.4 on a Java 7 JVM would therefor be very welcome.

We have quite a lot of of our own code built on top of Magnolia 4.4 and we plan 
on migrating to 4.5, but because of the API changes this will be a big project 
for us and we'll need to find a couple of weeks of free time for this…

Nils.

----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to