Howdy,
I've been doing a little bit of PostGIS QA this week, as a few wriggling
bugs still live on.
Changes include:
- exposing the ConnectionPool (this is mostly so tests may obtain a
connection and create tables)
- PostgisDBInfo object (encapsulated version info -- since several
methods were
GeoTools Does not support DataSource from an application server
---
Key: GEOT-951
URL: http://jira.codehaus.org/browse/GEOT-951
Project: GeoTools
Issue Type: Bug
Component
Justin Deoliveira a écrit :
> I have tried a couple of things now.
>
> 1. using java 1.5
> 2. commenting out all teh custom geotools javadoc sutff.
>
> Neither have worked, I get the same error. The only thing that does work
> is taking epsg-hsql out of the build.
So, its suggest that custom tag
PostgisDataStore does not close connection pool on disposal
---
Key: GEOT-950
URL: http://jira.codehaus.org/browse/GEOT-950
Project: GeoTools
Issue Type: Bug
Components: data
Website chaos
-
Key: GEOT-949
URL: http://jira.codehaus.org/browse/GEOT-949
Project: GeoTools
Issue Type: Bug
Components: admin
Affects Versions: 2.2.0
Reporter: Cory Horner
Assigned To: James M
jdbc1Datastore getConnection method is not thread safe
--
Key: GEOT-948
URL: http://jira.codehaus.org/browse/GEOT-948
Project: GeoTools
Issue Type: Bug
Components: core main
A
The implementation of AttributeExpression allows for features of differnt
types or shchemas. Having this method assumes only one. It would be nice
if the two were consistent.
-Justin
On Fri, September 22, 2006 12:25 pm, Andrea Aime wrote:
> Andrea Aime ha scritto:
>
>> Hi,
>> I'd like to ask perm
Ciao Andrea,
the plugin has its own unit tests. I am working on producer a smaller
testing data set and to increase a little bit the code coverage to
reach 60%.
I need it for geoserver-raster, hence it would be great to have it
under plugins within the end of next week if possible.
Thanks,
Simone
I also find it to be a pain when I just want to compile. I wonder if it
would make sense to put the formatting stuff into a profile so that it is
not run by default. The idea being that you should compile with that
profile before a commit.
-Justin
On Fri, September 22, 2006 1:01 pm, Gabriel Roldá
I have tried a couple of things now.
1. using java 1.5
2. commenting out all teh custom geotools javadoc sutff.
Neither have worked, I get the same error. The only thing that does work
is taking epsg-hsql out of the build.
-Justin
On Fri, September 22, 2006 8:47 am, Martin Desruisseaux wrote:
>
hi all,
is there a way of turning off the autoformating stuff while doing mvn
eclipse:eclipse? having a boring time waiting till it ends and need to run
that goal quite frequently
regards
--
Gabriel Roldán ([EMAIL PROTECTED])
Axios Engineering (http://www.axios.es)
Tel. +34 944 41 63 84
Fax.
Hi,
I'd like to ask permission to expose getSchema out of AttributeExpression,
because some visitors may uses that to infer attribute properties.
In particular, in one use case I need to check if the attribute I'm using
is the default geometry or not.
What do you think
Cheers
Andrea Aime
Andrea Aime ha scritto:
> Hi,
> I'd like to ask permission to expose getSchema out of AttributeExpression,
> because some visitors may uses that to infer attribute properties.
> In particular, in one use case I need to check if the attribute I'm using
> is the default geometry or not.
>
> What do
remove final modifier in arcsde dummy api
-
Key: GEOT-947
URL: http://jira.codehaus.org/browse/GEOT-947
Project: GeoTools
Issue Type: Bug
Components: data arcsde
Affects Versions: 2.2.1,
Hi,
thanks Martin for the suggestion, but I think it is not that important to be
that friendly with someone building the jar, but with the final users that
just download the arcsde plugin and expect it works. Since our only way of
creating a release, even if we have a profile, is against the dum
Justin Deoliveira a écrit :
> Hi Martin, I will try this workaround. However I am not sure the pain is
> worth it just to have the ability to use java 1.5 javadoc tags.
>
> I would vote for removing the 1.5 dependency, anyone else?
Actually I'm not sure that this is the cause - unknown tag should
Hi Martin, I will try this workaround. However I am not sure the pain is
worth it just to have the ability to use java 1.5 javadoc tags.
I would vote for removing the 1.5 dependency, anyone else?
-Justin
On Thu, September 21, 2006 5:48 pm, Martin Desruisseaux wrote:
> Justin Deoliveira a écrit :
Simone Giannecchini ha scritto:
> Hi guys,
> I am sending this email to ask permission to add a new coverage plugin
> called ImagePyramid.
> Guys present at FOSS might have seen it at work. What it does is
> basically managing a pyramid of mosaics of images going from really
> high resolution to re
18 matches
Mail list logo
