On 27/11/2009, at 8:12 PM, Jacques Le Roux wrote:
From: Scott Gray scott.g...@hotwaxmedia.com
On 27/11/2009, at 12:06 PM, Adam Heath wrote:
Scott Gray wrote:
Yeah +1 from me, I just wanted to make sure we had some tangible
benefits in mind and I didn't really see the dbcp library
problem
Jacques Le Roux wrote:
1) I proposed initially jdk 1.6 move because of the DBCP issue. I agree
now with Scott. Maybe we can wait to be in a situation that
really forces us to move ahead. It's simply pragmatic: why working on an
issue that does not exist yet? Even if we are sure we will
cross
Adam Heath wrote:
Scott Gray wrote:
I'm not necessarily against it but I'm yet to hear what we actually gain
by doing so, what are these changes that we could optionally make once
we stop supporting 1.5? With the change from 1.4 to 1.5 it was pretty
clear because of things like generics.
Scott Gray wrote:
Yeah +1 from me, I just wanted to make sure we had some tangible
benefits in mind and I didn't really see the dbcp library problem we had
as being a good reason for the switch since it was easily resolved.
Plus 1.6 hotspot is wicked smarter, and faster.
==
void foo() {
+1
Furthermore, on a debian lenny server, there is no jdk 1.5 in the
repository...
So, in order to make this migration, what are the required steps ? How
can we divide the work to be done ?
Cheers
Le 14/11/2009 05:44, Tim Ruppert a écrit :
../..
--
Erwan
OFBiz already runs fine on 1.6, so this would just be a matter of updating
documentation and such, and then people could optionally make changes that
require 1.6.
If everyone is in favour of this, we might as well get a vote going...
-David
On Nov 23, 2009, at 11:20 AM, Erwan de FERRIERES
I'm not necessarily against it but I'm yet to hear what we actually
gain by doing so, what are these changes that we could optionally make
once we stop supporting 1.5? With the change from 1.4 to 1.5 it was
pretty clear because of things like generics.
Regards
Scott
HotWax Media
Optional changes would include the code contained in
UtilProperties.java. Java 6 improves support for extending
ResourceBundle. Some of the code in there mimics Java 6 classes, so the
change would be straightforward.
-Adrian
Scott Gray wrote:
I'm not necessarily against it but I'm yet to
Scott Gray wrote:
I'm not necessarily against it but I'm yet to hear what we actually gain
by doing so, what are these changes that we could optionally make once
we stop supporting 1.5? With the change from 1.4 to 1.5 it was pretty
clear because of things like generics.
NavigablMap, which is
Le lundi 23 novembre 2009 à 15:32 -0600, Adam Heath a écrit :
Scott Gray wrote:
I'm not necessarily against it but I'm yet to hear what we actually gain
by doing so, what are these changes that we could optionally make once
we stop supporting 1.5? With the change from 1.4 to 1.5 it was
On 24/11/2009, at 11:19 AM, Matthieu Bollot wrote:
Le lundi 23 novembre 2009 à 15:32 -0600, Adam Heath a écrit :
Scott Gray wrote:
I'm not necessarily against it but I'm yet to hear what we
actually gain
by doing so, what are these changes that we could optionally make
once
we stop
There are some API things that are better in 1.6, and not compatible with the
1.5 API, but they all seem to have some sort of work around. For some of those
things we'll get better performance and maybe better flexibility (and maybe
less code to maintain) if we use the 1.6 API.
IMO the
+1
cheers, manuel.
On 14 Nov 2009, at 05:44, Tim Ruppert wrote:
+1 - I totally agree. People can always run the release branch if
they need to stay on 1.5, but the show must go on!
Cheers,
Ruppert
On Nov 13, 2009, at 9:32 PM, David E Jones wrote:
We had to make this decision before
Hi devs,
I don't remember why we still use 1.5. Here is a thread from 2006
http://markmail.org/message/5j5es63hpsh543ct.
Maybe it's time to think anew about it, don't you think so ?
Jacques
Running OFBiz on 1.6 is a good idea, because (Sun claims) 1.6 performs
better than 1.5.
The downside is, there might be servers out there that don't have a 1.6
JRE available. I would like to see us move on to 1.6 (especially now
that 1.7 is near), but I'm concerned for existing installations.
Thanks Adrian,
So it's the same concern than 3 years ago, I will check...
Jacques
From: Adrian Crum adri...@hlmksw.com
Running OFBiz on 1.6 is a good idea, because (Sun claims) 1.6 performs
better than 1.5.
The downside is, there might be servers out there that don't have a 1.6
JRE
Sun :
Java SE Java SE for Business Support Road Map (JDKs End of Life)
http://java.sun.com/products/archive/eol.policy.html
1.6 supported systems
http://java.sun.com/javase/6/webnotes/install/system-configurations.html
15 supported systems
Thank you for the info! That certainly helps.
-Adrian
--- On Fri, 11/13/09, Jacques Le Roux jacques.le.r...@les7arts.com wrote:
From: Jacques Le Roux jacques.le.r...@les7arts.com
Subject: Re: jdk 1.5 or 1.6
To: dev@ofbiz.apache.org
Date: Friday, November 13, 2009, 11:46 AM
Sun :
Java SE
What is not clear to me is what are we missing out on by supporting
both as we currently do, I think DBCP is an odd case because they
obviously have tried to support 1.5 but it seems there are a couple of
very minor bugs that prevent that support.
Other than DBCP what would we actually
I will commit soon using DBCP r835956 and this problem will have dissapeared.
As not much as been done from Postgres to support JDBC 4 we don't need really to turn to new drivers OOTB and if someone needs them
(on another DB or context or what else) s/he could do it anyway but will have to
We had to make this decision before with 1.4 - 1.5, and if I remember
right from 1.3 - 1.4 too.
Sooner or later we need to deprecate support for 1.5 in order to move
on, and to more easily be able to update various libraries and such.
The 1.5 - 1.6 transition is a bit of a pain because
+1 - I totally agree. People can always run the release branch if
they need to stay on 1.5, but the show must go on!
Cheers,
Ruppert
On Nov 13, 2009, at 9:32 PM, David E Jones wrote:
We had to make this decision before with 1.4 - 1.5, and if I
remember right from 1.3 - 1.4 too.
Sooner
+1.
--
Ashish
On Sat, Nov 14, 2009 at 10:02 AM, David E Jones d...@me.com wrote:
We had to make this decision before with 1.4 - 1.5, and if I remember
right from 1.3 - 1.4 too.
Sooner or later we need to deprecate support for 1.5 in order to move on,
and to more easily be able to update
+1
--
Ashish
On Sat, Nov 14, 2009 at 10:14 AM, Tim Ruppert
tim.rupp...@hotwaxmedia.comwrote:
+1 - I totally agree. People can always run the release branch if they
need to stay on 1.5, but the show must go on!
Cheers,
Ruppert
24 matches
Mail list logo
