Justin Deoliveira ha scritto:
> I am a little confused... the patch does not seem to touch anything
> related to id handling. Am I missing something.
>
> As for null being the placeholder feature id, are you talking about in
> REsultSetFeature? What do you want to change it to?
>
> Id generatio
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1566/changes
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Hi Jody,
> I would like to hear back on your experience with reordering
> MapContext layers.
>
I've got something working now - still very draft code...
In branches/2.6.x_JMapPane_move/demo/mapwidget - I've added a class
MapLayerTable which works with a JMapPane object and displays a list
of lay
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1565/changes
Changes:
[jive] Do not use unqiue version numbers for the SNAPSHOTs
--
[...truncated 11406 lines...]
[INFO] [jar-collector:collect {execution: default}]
[INFO] [install:install]
[INFO] In
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1564/
--
[...truncated 1696 lines...]
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.226 sec
Running org.geotools.filter.text.ecql.ECQLNullPredicateTest
Tests run: 4, Failures: 0, Er
The failure looks to be based on over loading the osgeo repository
again (the jar indicated exists)
Error transferring file
org.opengis:geoapi-pending:jar:2.3-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
osgeo (http://download.osgeo.org/webdav/geoto
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1563/changes
Changes:
[ang05a] Create app-schema tests artifact so they can be referred by Geoserver
app-schema tests.
--
[...truncated 1720 lines...]
Running org.geotools.filter.text.cql2.CQLGeoOper
Good afternoon:
I have been catching our net.refractions.udig.libs refresh.xml script
up with the latest. The latest breakdown of maven repository
organizations
# used for stable releases
updateSnapshotURL=http://download.osgeo.org/webdav/geotools
# used for snapshot releases
updateStableURL
This may be something for Justin - not sure.
I tried switching over to the opengeo repository today (to grab
snapshot releases) and was unable to obtain 2.6-SNAPSHOTs for:
- gt-gml
-gt-mif
- gt-mysql
- gt-oracle-spatial
- gt-process
- gt-wps
And our old friend without source code:
- spatialdbbox-
Thanks very much for your support everyone - much appreciated.
> I expect the first couple of things to pay attention to are:
> - the remaining nominations (PMC will need to vote on any nominations
> that are accepted).
> - Andrea is composing a module cleanup page; that will eventually turn
> to
Thanks Justin:
I have updated the developers guide.
Thank you for accepting this nomination Michael.
Jody
On Mon, May 11, 2009 at 9:33 AM, Jody Garnett wrote:
> I was going to wait for the methods to settle down first; for example
> the batch feature event methods are in the wrong spot; I need
It looks like I am confusing gmail today ... let me try again.
Thanks Justin - that is all the votes in then.
Thank you for accepting the nomination Michael - I have added your
name to the developers guide.
I expect the first couple of things to pay attention to are:
- the remaining nominations
Sorry for the late vote. Definitely a +1.
-Justin
Jody Garnett wrote:
> +1
>
> And I think that is 75%.
>
> On Sat, May 9, 2009 at 12:22 AM, Ian Turton wrote:
>>
>> On Fri, May 8, 2009 at 8:49 AM, Michael Bedward
>> wrote:
>>> Thanks Jody, for the clarification and for the kinds words. Given
On Mon, May 11, 2009 at 10:41 AM, Justin Deoliveira
wrote:
> I am a little confused... the patch does not seem to touch anything related
> to id handling. Am I missing something.
Yes; the part where I am stuck on how to patch insert feature writer.
> As for null being the placeholder feature id,
I am a little confused... the patch does not seem to touch anything
related to id handling. Am I missing something.
As for null being the placeholder feature id, are you talking about in
REsultSetFeature? What do you want to change it to?
Id generation is a bit tricky. The way it is done now is
I would be content with 7 as well; would you like to make a motion and
we can update the developers guide?
On Mon, May 11, 2009 at 8:59 AM, Justin Deoliveira wrote:
>
>>
>> I personally find the GeoServer directions sensible, voting is
>> easier when the number of people is small, but not too sma
I was going to wait for the methods to settle down first; for example
the batch feature event methods are in the wrong spot; I need to move
them to a transaction state associated with the connection.
I will get the javadocs in order shortly; ie after I know we have the
problem licked. I will also
Justin I need a code review on the feature id handling; and the
handling of commit prior to this patch being acceptable to me:
1) BatchFeatureEvent should be notified of any change to FeatureId;
right now you are using null as an ID placeholder and I would like to
change that. I also wanted to ask
Nice work. I made a few minor comments for xml-po, some of the demo
modules, postgis module, and the emf demo modules.
I am also +1 on all the ones you flagged as remove. I am looking forward
to a smaller code base, it is long overdue.
-Justin
Andrea Aime wrote:
> Hi all,
> I've created a wiki
re geometryless module - it is in use by people using the 1.6 complex
schema support. I dont plan to do anything else with it: I hope to
retire it completely by using the app-schema support for complex data
types and the ability to handle SQL dialects in the jdbc-ng stack. It
has the status of a le
>
> I personally find the GeoServer directions sensible, voting is
> easier when the number of people is small, but not too small.
> For a project with 90+ modules the current 5 members is certainly
> a bit small, hard to get enough people to cover all point of views,
> yet going over 7 may make
Cool, just reviewed and made some comments on the jira issue.
-Justin
Jody Garnett wrote:
> Hi Justin:
>
> There is a patch ready for your review:
> - http://jira.codehaus.org/browse/GEOT-2327
>
> There is some additional work that could be done if interested; right
> now a batch feature event
It would also be nice if you added javadocs for all the methods added,
not just some. I have been striving to maintain consistency in the
Content* classes, as well as in the JDBC subclasses, that is a pattern I
like to keep on following :). For instance fireFeatureUpdated() has no
jabadoc, but
Looks like you have been busy Jody. One thing I ask, can you separate
"cleanup" commits. It makes commit logs hard to follow when they are
riddled with formatting changes. I am all for cleaning up the
formatting, just prefer they be done in a separate commit.
Jody Garnett wrote:
> Turns out the
Christian Müller ha scritto:
> Andrea, should we edit the wiki page directly ?.
I guess so. Just add a comment with your initials in the modules
you have an opinion for.
> As an example, I agreed with David Adler on the new db2-ng module, so
> there will certainly be not further development and
Andrea, should we edit the wiki page directly ?.
As an example, I agreed with David Adler on the new db2-ng module, so there
will certainly be not further development and no support for the old db2
module. We can and should remove it or move it for some time to unsupported
and remove it in th
Hi all,
I've created a wiki page to organise the module
maintainerships reassignment and cleanup, here is it:
http://docs.codehaus.org/display/GEOTOOLS/Modules+cleanup
Ideally, I would like to find a maintainer for each module,
and at least an expression of interest for unsupported
modules by some
Updating geometry fails to supply SRID; resulting in exception writing geometry
column
--
Key: GEOT-2476
URL: http://jira.codehaus.org/browse/GEOT-2476
Project: GeoTo
Hi Justin:
There is a patch ready for your review:
- http://jira.codehaus.org/browse/GEOT-2327
There is some additional work that could be done if interested; right
now a batch feature event is sent out on commit or rollback - one for
each feature type modified. This is a bit over kill; a single
Sorry for the confusion Andrea; I am confusing h2/hsql and hibernate;
I was thinking I should switch to test cases for H2 in order to test
event notification.
Jody
On Sun, May 10, 2009 at 8:36 PM, Jody Garnett wrote:
>>> notification code; I think I am being held up over some of the tests
>>> not
Jody Garnett ha scritto:
>>> notification code; I think I am being held up over some of the tests
>>> not working for postgis; perhaps I will switch to hibernate.
>> This last sentence need some clarification... makes no sense to me? ;-)
>
> When I last checked the jdbcng postgis was avoiding some
>> notification code; I think I am being held up over some of the tests
>> not working for postgis; perhaps I will switch to hibernate.
>
> This last sentence need some clarification... makes no sense to me? ;-)
When I last checked the jdbcng postgis was avoiding some of the tests
it could not pas
Jody Garnett ha scritto:
> Turns out the JDBCFeatureReader copy constructor just missed the
> feature source field; all tests now pass with the event notification
> code in.
>
> I am going to go on to write test cases covering the event
> notification code; I think I am being held up over some of
Christian Müller ha scritto:
> Another quick question about advantages / disadvantages about Sphinx. Is
> there a possibility for a spell check ?.
Right. There is no IDE like spell check, but you can:
- use the one built into the editor of choice. For example to edit
Sphinx files I used Gedit
34 matches
Mail list logo
