Can't wait to get a new mac :). (I have 10.5 on my machine but can't
install Java 6 on it yet)
On 5-Feb-09, at 11:22 AM, Martin Desruisseaux wrote:
> Jody Garnett a écrit :
>> My understanding was Java 6 was now available for the mac; although
>> perhaps it is included with the latest operatin
Michael Bedward a écrit :
> Some of us are going to be stuck with Java 5 for a while yet.
Well, as said in my previous email a "geotidy for geotools" mercurial clone may
be required anyway in order to reinject some deprecated methods that I removed.
Keeping this clone compatible with Java 5 will
Jody Garnett a écrit :
> My understanding was Java 6 was now available for the mac; although
> perhaps it is included with the latest operating system?
Java 6 is now bundled in MacOS 10.5, together with Maven 2.0.6 and Subversion
1.4.
Martin
---
Jody Garnett a écrit :
> I may propose another route - of bring GeoTools 2.6 to Java 6. Given our
> yearly release schedule I think I can get support for this. GeoServer
> will only be using GeoTools 2.6 for GeoServer 2.0; uDig is already using
> Java 6 on most platforms (and I am waiting word
Jody Garnett ha scritto:
> Do tell - I am trying to sort out what the market will look like for
> GeoTools; we were stuck at the Java 1.3 mark for years waiting on Java
> Enterprise Edition developers ... are we going to be caught in a similar
> trap?
Maybe? J2EE 6 is still not around and once
2009/2/5 Jody Garnett :
> Bleck - good think I am asking then :P
> My understanding was Java 6 was now available for the mac; although perhaps
> it is included with the latest operating system?
> - http://developer.apple.com/java/
Yep, OSX 10.5.x but ONLY on their recent 64-bit intel based macs.
Bleck - good think I am asking then :P
My understanding was Java 6 was now available for the mac; although perhaps
it is included with the latest operating system?
- http://developer.apple.com/java/
Jody
On Thu, Feb 5, 2009 at 4:16 PM, Michael Bedward
wrote:
> 2009/2/5 Jody Garnett :
> > Do tell
2009/2/5 Jody Garnett :
> Do tell - I am trying to sort out what the market will look like for
> GeoTools; we were stuck at the Java 1.3 mark for years waiting on Java
> Enterprise Edition developers ... are we going to be caught in a similar
> trap?
Certain Australian state government departments
Do tell - I am trying to sort out what the market will look like for
GeoTools; we were stuck at the Java 1.3 mark for years waiting on Java
Enterprise Edition developers ... are we going to be caught in a similar
trap?
Jody
Michael Bedward wrote:
> Some of us are going to be stuck with Java 5
Some of us are going to be stuck with Java 5 for a while yet.
Michael
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and
Martin Desruisseaux wrote:
> In addition I commited myself to help with the port of Geotidy to Java 5 so
> it
> can be used with GeoTools. So Geotidy may be back to Geotools if the
> community
> wants it. But it can't be back now because not enough functionalities are
> ready.
>
I may propo
Hello Landon
If you stick to GeoAPI interfaces, there is no change. Both GeoTools and
Geotidy
implement the same set of interfaces. This also means that you can try a
library
and switch to the other without any change in your code.
If you use directly GeoTools implementation classes, most of
In the next month or two I'd like to attempt to add some support for
reprojection of vector data using an existing Java CRS library. I'm
trying to decide between the library in deegree and the library in
GeoTools. Aside from the other technical arguments for choosing the
CRS code in GeoTools over d
13 matches
Mail list logo
