Inline...
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 8/19/2014 3:45 PM, Ron Wheeler wrote:
Java 6 is already 8 years old. Java 7 is 3 years old. Java 8 is pretty
new but worth considering if it is not a significant different from the
upgrade to Java 7.
How much work was involved in the switch from 6 to 7.
Unit tests fail in Java 7. They had to be modified.
The difference between versions of Log4j would not seem to be a big
advantage or a big problem. I did this on one of our projects and it was
pretty painless. I also switched from properties to xml and that was a 1
hour project for my simple system.
From a marketing/project adoption point of view, a product based on an
8 year old version of Java is a lot less attractive that one running on
the latest version.
It shows that the project team is on top of current technology and that
the project is active.
I don't think that people would care much about the version of log4j
when deciding whether to consider OfBiz.
True, that shouldn't affect those considering OFBiz. But sys admins
configure tools to analyze OFBiz logs, and the new format could break
those tools. Keep in mind there may be hundreds of production
deployments running on the R13 branch.
Those sys admins could configure the new logger to produce logs that
look like the old ones, but then that's extra work that they believe
they shouldn't have to do on a "stable" release, and so forth and so on...
I have not tried Java 8 so I can not comment on where problems can come
from.
Our move from 6 to 7 was pretty transparent but we did not have any code
developed with earlier versions of Java and did not try to retrofit new
Java 7 capabilities into existing code.
There is no Java 7 specific code in the trunk. The recent changes were
merely fixing compatibility issues with Java 6.
You have already done this so you know the extent of the effort required.
I don't have to do the work so.....
Ron
On 19/08/2014 10:16 AM, Adrian Crum wrote:
I don't have an opinion on this.
The "rule" has been to keep backports restricted to bug fixes only,
but we have a history of backporting various refactorings to make
branch maintenance easier.
From my perspective, the two things cancel each other out, and I end
up with no opinion.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 8/19/2014 2:34 PM, Jacopo Cappellato wrote:
Before I start the process of preparing the release files for the
first release of the 13.07 series and call a vote on it I would like
to get your feedback on a couple of topics.
Should we backport to it the recent switch to Java 7?
Should we backport to it the recent update to Log4j2?
The main reason I am asking this is that once we release the first
release out of 13.07, for sure we will not backport the
aforementioned upgrades (because they are not bugs); however the
13.07 releases will stay with us for at least 2 years and it would be
nice to do the migration to these new technologies now.
Thanks in advance,
Jacopo
