View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061220024453Lbuild.39
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chanc
Okay I am going to just keep this on the geotools list for a bit ...
Here is the stack trace:
> aused by: java.lang.NoClassDefFoundError:
> org/apache/commons/logging/LogFactory
> at
> org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:130)
> at
> org.apache.commons.be
We have a blocker on GeoTools 2.4 to check if the we can use OSGi to
wire up GeoTools (rather then FactorySPI) - if that is successful I
imagine we can break up libs into its component parts (and no longer
have this hack of an ant script to maintain).
If you want a real sad story you should hea
Okay we are back, added a dependency to beanutils 1.7.0; note even
without this dependency udig still functioned - I suspect we are running
a bunch of code on the edges to hack around the previous implementation
of LiteralExpression.
So Justin - are you going to update us to JTS-1.8 :-) Remembe
Yup, you will have to drag in commons-beanutils into the set of
libraries. One thing i just thought of for udig was the dependencies on
emf + xsd for the xml module. Although you probably aren't pulling that
dependency in are you? If you did I wonder if the eclipse class loading
system would save y
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061220013126
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to shar
Oh I spoke too soon :-) It seems some extra dependencies have been
sneaked in.
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/commons/beanutils/Converter
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Unknown Source)
> at sun.misc.Service$LazyIter
Just a quick report from uDig on trunk ...
Building today, straight from the deployed jars results in the following
export errors:
> Package 'org.opengis.catalog.capability' does not exist in this plug-in
> Package 'org.opengis.catalog.discovery' does not exist in this plug-in
> Package 'org.open
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061219232706Lbuild.38
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chanc
Chris Holmes a écrit :
> Is any of the projection stuff from google
> SoC in this release?
No. It is on trunk for the 2.4 release.
Martin
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's
Martin I have fixed the link for you, the README you use on the
SourceForge site seems to be a variation of the "Announcement". Usually
we take the readme right from the src download, it is much more detailed
and includes links to mailing lists, build instructions etc.
Jody
> Martin currently t
So that says how to run it ... :-D
The naming conventions should head on over to the coding standards section.
The last thing to make this complete (that I am not sure how to do) is
providing the JDBC DataStores tests their connection parameters as part
of the maven build system.
Jody
> Done.
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061219151705
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to shar
Adrian,
The release of the 19123 Primer (draft six) should help people understand
coverages. The implementation manual is being written in parallel with the
implementation itself. 19123 primer is 69 pgs and the "coverage core"
implementation unit is ~20 pages.
Remember Xwindows? There were two
Done.
http://docs.codehaus.org/display/GEOT/2.5.7+Testing+with+Maven
Jody Garnett wrote:
> Justin can you update the developers guide with examples for other
> module maintainers? Right now
> we have very little clue where to start.
>
> Thanks so much for restoring PostGIS testing.
> Jody
>> So
Justin can you update the developers guide with examples for other
module maintainers? Right now
we have very little clue where to start.
Thanks so much for restoring PostGIS testing.
Jody
> Sorry, forget to send an update I have enabled on line and stress via
> profiles using Andrea's method. Ho
Sorry, forget to send an update I have enabled on line and stress via
profiles using Andrea's method. However I have not enabled the profile
for all modules and there is still some work to be done by other module
maintainers to ensure that on line tests are good to go.
I have however enabled them
Martin Desruisseaux <[EMAIL PROTECTED]> wrote on 12/15/2006
09:35:20 PM:
> Bryce L Nordgren a écrit :
> > Item 1: "Geophysics" and stored portrayal
> > The 19123 coverage data type is not responsible for maintaining a
> > "rendered" version of itself. The "geophysics" flag is likely to
> > disa
Chris Holmes wrote:
> This is so written by programmers ;)
Ha ha - go chris go.
> Most people don't know what a 'GridCoverage' is. At least call it
> 'raster support' and list the particular coverage formats we've got.
> If you tell me what formats that are nice and fast that we're
> supporting
This is so written by programmers ;)
Most people don't know what a 'GridCoverage' is. At least call it
'raster support' and list the particular coverage formats we've got.
If you tell me what formats that are nice and fast that we're supporting
then I can make a more user friendly release an
Thanks for waiting Martin, thought I would run the page through a spell
checker first.
Jody
> Jody Garnett a écrit :
>> I will update the Announcement page for you, I always try to update
>> it to reflect the last release (that way the announcement
>> instructions turn into cut&paste).
>> - http
Jody Garnett ha scritto:
> Sounds good guys :-) Andrea as module maintainer for this one can I ask
> you to forward port your test cases to trunk? If they do not pass let me
> know and I can step in.
I did not find tests for the moment, but will do.
> I would like to confirm that trunk handles
Martin Desruisseaux wrote:
> Jody Garnett a écrit :
>> I will update the Announcement page for you, I always try to update
>> it to reflect the last release (that way the announcement
>> instructions turn into cut&paste).
>> - http://docs.codehaus.org/display/GEOT/Announcement
>>
>> Is this what
Matthias Basler wrote:
> Hi Jody, thanks for your reply.
> Unfortunately I have no idea about what the "iTunes dynamic playlist" is or
> how it looks, nor how playlists (as I known them) relate to defining ranges.
> Do you mind pointing me at some details/images that demonstrate your idea.
>
> Ot
Jody Garnett a écrit :
> I will update the Announcement page for you, I always try to update it
> to reflect the last release (that way the announcement instructions turn
> into cut&paste).
> - http://docs.codehaus.org/display/GEOT/Announcement
>
> Is this what you mean by short README text?
Ye
Andrea Aime a écrit :
> I like your implementation, will merge it into 2.3.x.
> Thank you for taking the time and improve the proposal :-)
Thanks :). I just realized that the very last line in "evaluate" ("return
value1.equals(value2);") could be "return false", since "value1.equals(value2)"
wa
Sounds good guys :-) Andrea as module maintainer for this one can I ask
you to forward port your test cases to trunk? If they do not pass let me
know and I can step in.
I would like to confirm that trunk handles the same list of concerns
both you and Martin have brought up. Just because we have
Matthias Basler wrote:
> Offlist ...
>
> Jody wrote
>
>> When I did this last time I modelled the result on the iTunes dynamic
>> playlist definition, they had a nice visual layout and a smooth way to
>> express other relationships beyond simple range checks (ie access to our
>> list of funct
Martin Desruisseaux ha scritto:
> Andrea Aime a écrit :
>> I've found various issues in IsEqualsToImpl as
>> found in 2.3.x. The original implementation is attached,
>> as well as a new implementation that should handle properly
>> most numeric cases.
>> The original implementation had various issu
Hi Matthias Basler:
We are still in the process of anouncing the 2.3.0 release (and updating
the home page will be part of that). Martin is apparently stuck writing
a "readme", but I am not too sure how to understand that ...
So please use 2.3.0 and enjoy your hacking,
Jody
> Hi Geotools guys,
Andrea Aime a écrit :
I've found various issues in IsEqualsToImpl as
found in 2.3.x. The original implementation is attached,
as well as a new implementation that should handle properly
most numeric cases.
The original implementation had various issues due to
numeric overflows and decimal part tr
Hi Geotools guys,
visiting your homepage (http://geotools.codehaus.org/Downloads) I found the
following a bit confusing:
"Stable Release: 2.2.2Recommended for new projects!
Development Release: 2.3.0Not ready yet, will release when
feature mo
Hi Andrea,
Seems like this is a problem that has been solved on trunk as well. I
understand that the changes there are not back portable to 2.3.x.
However we should ensure that the same behaviour is maintained.
I can't spot any problems with the routine you wrote. Perhaps the only
thing is that i
Justin Deoliveira ha scritto:
> Hi Andrea,
>
> Seems like this is a problem that has been solved on trunk as well. I
> understand that the changes there are not back portable to 2.3.x.
> However we should ensure that the same behaviour is maintained.
>
> I can't spot any problems with the routine
Justin Deoliveira ha scritto:
> Jody Garnett wrote:
>> That is a tough one, I need to ask if this is another cite test stepping
>> outside of the bounds of the ordinary (ie what is defined by the WFS
>> specification)?
> No, its perfectly valid in wfs to have a feature type with multiple
> geomet
Jody Garnett ha scritto:
> Andrea Aime wrote:
>> I don't know, I did not touch anything and for the moment I'm hacking
>> the versioned data store in a gt2 2.3.x checkout.
>> Hope today's geotools meeting results will allow me to move to trunk.
> Let's make that a point of success; just as with uns
Justin Deoliveira ha scritto:
> Hi all,
>
> I have run into a situation where it would be nice to have the jdbc sql
> encoders to be moved over to the geoapi FilterVisitor interface, instead
> of implementing the old interface and having the FilterVisitorWrapper be
> used for backwards compatabili
When I did this last time I modeled the result on the iTunes dynamic
playlist definition, they had a nice visual layout and a smooth way to
express other relationships beyond simple range checks (ie access to our
list of functions).
The work was commercial however, took a couple days of SWT pro
Rob Atkinson wrote:
> Once you have an example, I'll try to replicate with geometryless module
> (which I intend to move up to a supported state by 2.4 release).
>
> Some advice on how to handle the IP check with multiple JDBC driver
> libraries as targets would be helpful, as well as how to supp
Hi all,
I've found various issues in IsEqualsToImpl as
found in 2.3.x. The original implementation is attached,
as well as a new implementation that should handle properly
most numeric cases.
The original implementation had various issues due to
numeric overflows and decimal part truncations, and
Hi geotools community,
In several places in my styling widget I find the need for a graphical,
convenient GUI element that allows the user to select ranges and their
boundaries, for cases such as:
If x >= 0 and x < 1 do A
if x >= 1 and x <= 3 do B
if x > 3 do C
You get the picture...
Of cours
Once you have an example, I'll try to replicate with geometryless module
(which I intend to move up to a supported state by 2.4 release).
Some advice on how to handle the IP check with multiple JDBC driver
libraries as targets would be helpful, as well as how to support the
cruise control testi
Oracle does not encode like filters anymore
---
Key: GEOT-1077
URL: http://jira.codehaus.org/browse/GEOT-1077
Project: GeoTools
Issue Type: Bug
Components: data oraclespatial
Affects Vers
Andrea Aime wrote:
> Jody Garnett ha scritto:
>> A couple more sanity checks for after a proposal has been accepted:
>> - Clean up any code examples to follow the proposed API
> This shall be done after the proposal is accepted right?
Yes, although frankly code examples are the *best* way to review
Jody Garnett ha scritto:
> A couple more sanity checks for after a proposal has been accepted:
> - Clean up any code examples to follow the proposed API
This shall be done after the proposal is accepted right?
This also calls for having an easy way to locate all code examples.
Are they all in the
45 matches
Mail list logo
