The main module tests pass fine with Java 4 but fail with Java 6 (now in final
release). JUnit test reports attached.
Martin
---
Test set: org.geotools.data.DataUtilitiesTest
-
Hi Chris you are running into a design principle I am trying to follow here:
- access to the original format of the model (I assuming the
FeatureSource subclass will step in with the FeatureType definition you
are used to at a later point of time). This is the lesson I learned with
all the meta
I'm happy to volunteer. I could co-volunteer with acuster, or let him
have it, and just play the role of 'the board member'.
Chris
Jody Garnett wrote:
Hi Everyone, I am getting involved in some J2EE projects at work and am
scaling back my geotools involvement to volunteer time :-)
Currently
> Happened over a couple of meetings; posted a wiki page asking for
> feedback etc...
Can we get a link to that wiki page? I still don't quite understand the
justification for this new API? I like the theory of a super class to
getting coverages and features, but it seems it'd be more appropri
Jody Garnett wrote:
> Justin Deoliveira wrote:
>> So looking down the pipe at a major api shift ( fm ), we are already
>> planning for another ( data )? How do we sell this api change? From a
>> client point of view I can see the advantage, but what does it buy
>> others besides another layer of ab
Justin Deoliveira wrote:
> So looking down the pipe at a major api shift ( fm ), we are already
> planning for another ( data )? How do we sell this api change? From a
> client point of view I can see the advantage, but what does it buy
> others besides another layer of abstraction.
>
This is do
So looking down the pipe at a major api shift ( fm ), we are already
planning for another ( data )? How do we sell this api change? From a
client point of view I can see the advantage, but what does it buy
others besides another layer of abstraction.
>From a GeoServer point of view the only gain I
Justin Deoliveira wrote:
> Ok, I apologize for the assumption that this code came from udig. I saw
> the use of generics and assumed. So now that I have more information, I
> will do a method by method review.
>
Nope that was by way of making things clear when JPox-Spatial was
implementing.
>
Ok, I apologize for the assumption that this code came from udig. I saw
the use of generics and assumed. So now that I have more information, I
will do a method by method review.
GeoResourceInfo getInfo();
Link to the catalog. Unfortunatley not everyone uses a catalog and the
catalog api has
http://docs.codehaus.org/download/attachments/31212/ISO19123+Primer.pdf
Draft 6 of ISO 19123 Primer is released.
Draft 6 represents a major reorganization of the primer. Prior to
this release, the document grew by addition, meaning that I wrote about
what I was learning at the time. There was no
Justin Deoliveira wrote:
> Hi guys,
>
> I am looking over these interfaces and they seem to be an abstraction of
> the datastore api. This is kind of out of left field if you ask me,
> perhaps i missed discussion on the list about this.
>
Happened over a couple of meetings; posted a wiki page as
Hi Justin
Thanks for your input. The link to the existing API is, that at a later stage
DataStore should extend DataAccess, FeatureSource should extend Source, etc. If
you want to see an example of an implementation of the new interfaces have a
look
at unsupported/jpox. I agree with you that w
Hi guys,
I am looking over these interfaces and they seem to be an abstraction of
the datastore api. This is kind of out of left field if you ask me,
perhaps i missed discussion on the list about this.
I see links to the catalog api, but none to the datastore api. Is there
a link? I realize there
Good point Martin;
I have created the following jira QA blocker against 2.4.0 to ensure the
@since and other QA checks are dealt with before 2.4.0 goes out the door:
- http://jira.codehaus.org/browse/GEOT-1063
> Could it be that the trouble in building Geoserver against
> Geotools-trunk is parti
I guess if you are willing to update all the visitors, however these
literal constants form a closed set, so making additions should not be
taken lightly. Its not an api breakage, but someone out there who has
written an expression visitor may find there code breaks.
-Justin
Andrea Aime wrote:
>
Data Access API QA Review
-
Key: GEOT-1063
URL: http://jira.codehaus.org/browse/GEOT-1063
Project: GeoTools
Issue Type: Improvement
Components: admin
Affects Versions: 2.4.0
Reporter: Jody Ga
Hi Everyone, I am getting involved in some J2EE projects at work and am
scaling back my geotools involvement to volunteer time :-)
Currently the only responsibility of our OSGeo representative is to get
us through the incubation process. I am pleased with what I have
accomplished; we now know w
Thx Martin
:-)
Simone.
On 12/11/06, Martin Desruisseaux <[EMAIL PROTECTED]> wrote:
> Simone Giannecchini a écrit :
> > I added a plugin page at the wrong level and I would like either to
> > remove it or to just move it somewhere else.
>
>
> "Page Operations" , "Edit", then edit the "Parent page"
Simone Giannecchini a écrit :
> I added a plugin page at the wrong level and I would like either to
> remove it or to just move it somewhere else.
"Page Operations" , "Edit", then edit the "Parent page" field.
Martin
--
How do I remove a page from teh geotools website?
I added a plugin page at the wrong level and I would like either to
remove it or to just move it somewhere else.
Simone.
On 12/11/06, Simone Giannecchini <[EMAIL PROTECTED]> wrote:
> I know ;-(.
>
> Simone.
>
> On 12/11/06, Jesse Eichar <[EMAIL P
Thanks Jesse:
Epsg-WKT - are we going to keep using this for uDig (or is it time to
tip this in the bit bucket?)
IanT is the module maintainer for MapPane, given the number of questions
on the user list unsupported seems a fair call.
Jody
> The latest list of modules that will be moved to "unsu
I know ;-(.
Simone.
On 12/11/06, Jesse Eichar <[EMAIL PROTECTED]> wrote:
> The latest list of modules that will be moved to "unsupported" is now:
>
> Unsupported Plugins:
> ArcGrid
> Epsg-WKT
> GeoTiff
> Image
> ImageMosaic
> ImagePyramid
>
> Unsupported Extensions:
> MapPane
>
>
> Looks like Sim
Hi all,
I apologize for missing last week's meeting (I had an exam), but I also
will not be able to attend today's meeting, nor any meeting between now
and 12. (So I should be there for the 15th) I'll be on vacation in
northern Europe.
Cheers,
Richard
--
Adrian Custer a écrit :
> gt2-2.3.0-bin.zip has both:
> gt2-referencing-2.3.0.jar
> and
> gt2-referencing-2.3.0-RC1-SNAPSHOT.jar
>
> do you know what's going on there?
I was not aware of that. Looking on the 2.3.0 tag, I see two possibilites:
* I noticed that the "coverage_development" dire
The latest list of modules that will be moved to "unsupported" is now:
Unsupported Plugins:
ArcGrid
Epsg-WKT
GeoTiff
Image
ImageMosaic
ImagePyramid
Unsupported Extensions:
MapPane
Looks like Simone has a couple of page to make up? ;-)
Jesse
On 7-Dec-06, at 10:30 AM, Jody Garnett wrote:
> O
Fair enough. I'm not going to be as verbose as Andrea but I'll
outline our plans for uDig.
1. The list of bugs on the 1.1 road map is around 25 or so once they
are patched 1.1 will be released officially.
2. 1.1.1 will be release very shortly after and in an odd move it
will be based on G
Thanks Cory :-)
I noticed you did not list a Jira category; do you want one set up?
Your review.txt file lists an apache license (so you are going to have
to think things through, for now can you create an APACHE_LICENSE.txt
file next to the existing LICENSE.txt file.
Jody
> Jody Garnett wrote
Jody Garnett wrote:
>One of the "reasonable" request for supported modules was a wiki page
>showing end-users how the module is doing. The timeline for this was
>the 2.3.0 release; which has just occurred (see
>http://docs.codehaus.org/display/GEOT/Supporting+your+module).
>
>
Page created:
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061211134154Lbuild.14
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chanc
On Fri, 2006-12-01 at 20:57 -0500, Martin Desruisseaux wrote:
> What remains to be done:
...
>- Tests the Sourceforge zip files
Martin,
gt2-2.3.0-bin.zip has both:
gt2-referencing-2.3.0.jar
and
gt2-referencing-2.3.0-RC1-SNAPSHOT.jar
do you know what's going on there?
--adrian
---
Hi,
our current literal expressions do not support directly longs,
and this is very bad if you have longs in a db.
You create a literal with a long, say for example, Long.MAX_VALUE,
it gets encoded into a double with reduced precision, and as
a result the query that the sql encoders produce is inc
Constants in Dummy jars are not binary compatible with those in the ArcSDE jars
---
Key: GEOT-1062
URL: http://jira.codehaus.org/browse/GEOT-1062
Project: GeoTools
I
The reporting app still says its broken:
http://geo.openplans.org:9090/
The latest build log reports a complication failure in the wfs module
http://geo.openplans.org:9090/buildresults/geotools-trunk
The last message I got about trunk was on the 8th, at 16:19 and it
reports failure. Perhaps you
Did you fix them? Because the build messages I've got say that the
build is fixed so I didn't worry about it.
Jesse
On 11-Dec-06, at 6:40 AM, Justin Deoliveira wrote:
> Hi Jesse,
>
> Seems the build is still broken. plugin/wfs has some compliation
> errors.
> Looks like a patch must have be
Hey all,
Moving the 2.3.0 release forward slowly, I've updated the web site
download page to add 2.3.0.
On Fri, 2006-12-01 at 20:57 -0500, Martin Desruisseaux wrote:
>
> What remains to be done:
>
>- Provides a "Readme" file to the SourceForge download.
>- Tests the Sourceforge zip fil
Hey all,
once again we have added pages willy nilly to the website. I'm hereby
threatening to cleanup by reparenting pages into the RnD page.
The tree view of the web site:
http://docs.codehaus.org/pages/listpages-dirview.action?key=GEOTOOLS
shows a bunch of pages which are floating at the top
Andrea Aime wrote:
> Martin Desruisseaux ha scritto:
>> Andrea Aime a écrit :
>>> * to fix this, is it simply ok to checkout the 2.2.2 tag,
>>>build and do a mvn deploy?
>>
>> I think that it work. It should overwrite the 2.2.2 JARs files.
>>
>>> * since the tag gets checked out during releas
Martin Desruisseaux ha scritto:
> Andrea Aime a écrit :
>> * to fix this, is it simply ok to checkout the 2.2.2 tag,
>>build and do a mvn deploy?
>
> I think that it work. It should overwrite the 2.2.2 JARs files.
>
>> * since the tag gets checked out during release:perform,
>>I guess the
Andrea Aime a écrit :
> * to fix this, is it simply ok to checkout the 2.2.2 tag,
>build and do a mvn deploy?
I think that it work. It should overwrite the 2.2.2 JARs files.
> * since the tag gets checked out during release:perform,
>I guess the release instructions do miss something abou
Andrea Aime wrote:
> Hi,
> apparently release:prepare does a bad job even on the tag
> that's used to perform the release, as a result I have
> one user complaining that there are 2.2.2 deployed poms
> that do refer 2.2.3-snaphost.
>
> Two questions:
> * to fix this, is it simply ok to checkout th
Hi,
apparently release:prepare does a bad job even on the tag
that's used to perform the release, as a result I have
one user complaining that there are 2.2.2 deployed poms
that do refer 2.2.3-snaphost.
Two questions:
* to fix this, is it simply ok to checkout the 2.2.2 tag,
build and do a mvn
Hi Jesse,
Seems the build is still broken. plugin/wfs has some compliation errors.
Looks like a patch must have been brought acrross that didn't take into
account that Filter.ALL is now Filter.EXCLUDE.
-Justin
[EMAIL PROTECTED] wrote:
> View results here ->
> http://geo.openplans.org:9090/build
CreateSchema tests fail because of quoting issues
-
Key: GEOT-1061
URL: http://jira.codehaus.org/browse/GEOT-1061
Project: GeoTools
Issue Type: Bug
Components: data postgis
Affect
A new bugfix release for the 2.2.x series.
Bug fixes are really all over the place, rendering, Oracle, shapefiles,
and more, see a full changelog with details here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10270&styleName=Html&version=12963
Download links here:
http://docs.codeh
44 matches
Mail list logo
