Justin Deoliveira ha scritto:
Nice, thanks for setting that up Andrea. Configurations look good. I
just had to tweak index.html for the 2.0.x nightlies which was still
pointing back to 1.7.x.
Also +1 on killing the old builds.
What we could do for 1.7.x is simply disable the build, but
Hi all,
with this mail I'm trying to start discussion on this controversial
subject: shall we switch to Java 6 as the minimum requirement for
GeoTools (and GeoServer/uDig?).
Pros for Java 6
- we can use more up to date API
- most developers nowadays have it installed
- Sun is ending support for
Although I'm new on this list, but I wouldn't mind seeing GeoTools make
the switch to Java6 over time.
I would assume IBM is working hard on getting this up and running, so +1
from me.
Andrea Aime schreef:
Hi all,
with this mail I'm trying to start discussion on this controversial
subject:
Hi Andrea,
Regarding Macs, Java 6 was available in OSX 10.5 (Leopard) but only
worked with 64 bit machines. Those with older hardware (like me) have
to upgrade to 10.6 (Cold Cat as Jody calls it) to be able to run Java
6 on our 32 bit machines.
I haven't done this yet because there seemed to be
I think that switching to Java 6 would be okay for 2.7 series; +1
- Same goes for OSX? I think that people are forced to pay
the Apple tax in order to get a working Java 6?
(aka upgrade to snow leopard?)
That is correct.
Jody
Michael Bedward ha scritto:
Hi Andrea,
Regarding Macs, Java 6 was available in OSX 10.5 (Leopard) but only
worked with 64 bit machines. Those with older hardware (like me) have
to upgrade to 10.6 (Cold Cat as Jody calls it) to be able to run Java
6 on our 32 bit machines.
I haven't done
-1 from my side for the geoserver base (2.6). The most common Websphere
installations are 6.x based on Java 5.
Is there a point in time where we plan to use 2.7.x for geoserver ?
We should support at at least 2 java versions, so I would wait until the
first app servers use java 7. At this
Christian Müller ha scritto:
-1 from my side for the geoserver base (2.6). The most common Websphere
installations are 6.x based on Java 5.
Is there a point in time where we plan to use 2.7.x for geoserver ?
The current GS trunk, which is probably turning into 2.1 release in a
few months (6
Andrea Aime ha scritto:
Christian Müller ha scritto:
Makes sense. Wondering how we'd go about dealing with java 5 not being
downloadable anymore from Sun sites. My worry is more or less about
how hard it is to get new developers contributing to GeoTools (anyone
of us already has copies of
I think you dont overstate the problem. A quick look on the ibm donload page
http://www.ibm.com/developerworks/java/jdk/index.html?S_TACT=105AGX02S_CMP=
HP shows the same problem. You get all versions for ix systems. but only the
java runtime for windows. I remember that I tried to get an ibm
Can I confirm that the weekly builds deploy a snapshot? If so I think
we are good to go.
Jody
On Wed, Nov 4, 2009 at 7:47 PM, Andrea Aime aa...@opengeo.org wrote:
Justin Deoliveira ha scritto:
Nice, thanks for setting that up Andrea. Configurations look good. I
just had to tweak index.html for
11 matches
Mail list logo
