Afternoon Brett:
Please keep in mind that Java 7 is being discussed in terms of a build box
profile. As of yet no build box configured for Java 7 has been asked for or
volunteered.
This discussion is in part to gauge interest in supporting Java 7.
With that in mind here is the only thing I wou
In practice, no. While the bytecode versioning is well defined, runtime
changes break compatibility. To take an example seen a few days ago, in
Java 7 the FileChannel interface has a new interface
SeekableByteChannel. Implementations of FileChannel compiled with Java 7
(even with target 6 as we
While I see the need to maintain Java 6 compatibility (build and run on Java
6), it should be Java 7 compatible also.
I build and develop within both environments. I have successful builds on
Windows 7 (x64) using Java JDK 7; so there is some definitely some support
provided already.
I underst
Edward,
I recall from an earlier email that you have a non UTF-8 locale:
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: /home/ejudge/Downloads/jdk1.6.0_45/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
I think this is a synonym for ASCII.
The problematic test con
Point taken. I guess I had assumed 7 was fairly "safe" now. Our IT
management certainly values deferred maintainance too :-)
However, they can also get shirty about products that are dependent on
no-longer supported software as well. You run into the situation where
product A depends on version
On 11/06/13 05:36, Phil Scadden wrote:
> On 11/06/2013 1:40 a.m., [email protected] wrote:
>> Java 6 is put out to pasture? Not even an security updates...
>> Q: Java 7 minimum? Terrible idea
>> Q: Java 7 compile? Additional work to support both - discuss on mailing list
> At risk of wadi
On 11/06/2013 1:40 a.m., [email protected] wrote:
> Java 6 is put out to pasture? Not even an security updates...
>
> Q: Java 7 minimum? Terrible idea
> Q: Java 7 compile? Additional work to support both - discuss on mailing list
>
At risk of wading in where angels fear to tread, but is j
I am seeing an failure when building the geotools code that looks like
this:
WARNING: Creating geom with null CoordinateReferenceSystem - did you mean
to setCRS?
Jun 7, 2013 11:19:24 AM org.geotools.renderer.style.FontCache loadFromUrl
INFO: Bad file name in SLDStyleFactorynotExistingFont
java.i
Catching up with this thread!
> Checked it over, looks good. I may of missed it in the test cases, did you
> support encoding on this one?
>
>
It was pointed out in the Skype meeting that I need to be more clear :-D
I was trying to ask if XML output can be generated from an InternationalStri
GeoTools / GeoServer Meeting 2013-06-10
===
Attending
-
Ben Caradoc-Davies
Andrea Aime
Jody Garnett
Justin Deoliveira
Alessio Fabiani
Jukka Rahkonen
Agenda
--
- Update on Previous Action Items
- GeoTools 9.3 / GeoServer 2.3.4 Release
- WFS 1.0 C
Andrea Ai
>
> This totally makes sense, thank you.
> Hum... cpdetector is half a megabyte, a wee bit too large.
>
Yes, I know.
> However, the xml declaration is just one line, and I believe that one can
> be read before reading the actual content.
> Actually, see this one, it seems a parser can read the e
Hi,
here is the usual reminder about the meeting... sorry to be late, last
Friday I was out...
http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools%2FGeoServer+meeting&iso=20130610T13&p1=1440
Cheers
Andrea
--
==
GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoser
On Mon, Jun 10, 2013 at 9:11 AM, Mauro Bartolomeoli <
[email protected]> wrote:
> From my experience, it's not the parser duty to handle the encoding. This
> is usually done building a Reader using this weird syntax:
>
> new InputStreamReader(, encoding)
>
> but this assumes you
2013/6/9 Andrea Aime
> On Sun, Jun 9, 2013 at 4:14 PM, Jody Garnett wrote:
>
>> Created a pull request for this:
>> https://github.com/geotools/geotools/pull/202
>>
>> Updated both gt-styling (in main) and gt-xsd-sld to support the new
>> extension.
>>
>> Checked it over, looks good. I may of mis
15 matches
Mail list logo