See http://hudson.opengeo.org/hudson/job/geotools-trunk/1422/changes
Changes:
[jive] explicitly ignore geoapi-dummy-pending to restore build; no explicit
dependeny on geoapi from unsupported/geometry to avoid tripping up on
dummy-pending clash
--
Hello Jive
Its look like that the switch to GeoAPI 2.3-SNASHPOT is causing issue; I'm
sorry
for that. Do you want me to take the hand on that?
Martin
--
Open Source Business Conference (OSBC), March 24-25,
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1423/changes
Changes:
[mbedward] removed mappane demo from build
[mbedward] removing existing mappane demo
--
[...truncated 8387 lines...]
[INFO] Building Next Generation JDBC DataStores
[INFO]
Thanks muchly - I am going to review tomorrow morning (during my weekly
office hours) and hopefully produce some nice docs. When at work I will
deploy a 2.6-SNAPSHOT and we can ask interested parties on the user list
to try out the code / docs.
fun fun fun
Jody
Michael Bedward wrote:
oops -
cheers mate
I'll put a simple demo up as well tomorrow to illustrate the story so far
Michael
2009/3/2 Jody Garnett jody.garn...@gmail.com:
Thanks muchly - I am going to review tomorrow morning (during my weekly
office hours) and hopefully produce some nice docs. When at work I will
deploy a
Aside be careful to build; after you remove the jmappane sample use
demo; the demo/introduction failed because it made use of that module.
Hopefully we can revise demo/introduction to use your new api tomorrow?
Jody
Michael Bedward wrote:
cheers mate
I'll put a simple demo up as well
Andrea Aime wrote:
Hi,
my GeoTools build is broken even after trying a -U build with
the following error message:
/home/aaime/devel/gt2-trunk/modules/library/main/src/main/java/org/geotools/styling/StyleFactoryImpl.java:[40,25]
cannot find symbol
symbol : class ExtensionSymbolizer
Ciao Andrea,
as you know this problem has been bothering us as well, we have
customized geoservers in production that serve remote sensing layers
acquired daily where this issue has popped up once in a while.
I am +1 about applying the patch, since as you point out, right now
referencing is more
Hi Andrea:
A while ago you talked about using an Expression (rather than a
PropertyName) in Rule; we have a similar thing in the symbolizers where
Expressions is already allowed.
At the time our conversation got stuck based on how to calculate the
effective bounds of an expression (with a
Hi Andrea;
I deployed the GeoAPI 2.3-SNAPSHOT and made sure to delete mine and do a
local build before committing. This is obviously my mistake and I will
look at it now.
Can you confirm that maven downloaded GeoAPI 2.3-SNAPSHOT?
Jody
Andrea Aime wrote:
Hi,
my GeoTools build is broken even
On Tue, Mar 3, 2009 at 2:58 AM, johann sorel johann.so...@geomatys.frwrote:
Hi again,
I've just maid my first complete review of the styleFactory.
the major things I have fixed :
- missing rotation parameter on several creation methods
Good catch.
- symbolizer creation methods wanted an
Hello Andrea
The problem you are pointing can be solved in a simplier way...
A deeper analysis shows an architectural problem with the sql
based EPSG factories, in particular, they get a hold on a single
SQL connection and try to perform every operation against it,
without any possibility
I take that back; it looks some changes were deployed to GEOAPI I was
unaware of trying to fix the build now.
Jody
Jody Garnett wrote:
Hi Andrea;
I deployed the GeoAPI 2.3-SNAPSHOT and made sure to delete mine and do
a local build before committing. This is obviously my mistake and I
will
Martin Desruisseaux wrote:
Hello Andrea
The problem you are pointing can be solved in a simplier way...
A deeper analysis shows an architectural problem with the sql
based EPSG factories, in particular, they get a hold on a single
SQL connection and try to perform every operation
sorry about that - I'll fix up the introduction now
Michael
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
Hum we should do something about this. From what I see whoever
is working on GeoApi changes is not making the corresponding
GeoTools changes. Shall we sit on a specific GeoApi build?
Cut a GeoApi relase? Or just get off GeoApi so that GeoTools can
have back some control on its destiny?
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1425/changes
Changes:
[mcr] Improving user interface of utilities on 2.6.x
--
[...truncated 789 lines...]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running
Andrea your patch sounds similar to the work I did in the referencing
module; where everything was moved over to DataSource internally; and a
connection was created as needed. It may not be directly similar since a
pool of workers was kept each with a connection and cache; but they
would be
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1426/changes
--
[...truncated 780 lines...]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
Running org.geotools.referencing.FactoriesTest
Mar 2, 2009 5:10:25 PM
Jody Garnett wrote:
Hi Andrea:
A while ago you talked about using an Expression (rather than a
PropertyName) in Rule; we have a similar thing in the symbolizers where
Expressions is already allowed.
At the time our conversation got stuck based on how to calculate the
effective bounds
What bothers me more is how changes to geoapi have been handled
recently. In some cases ( like Ben's proposed changes ) it seems a
formal proposal is needed.
I missed this conversation about Ben's proposed changes; what are they? I
was not signed up to the mailing list for a bit - in general
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1427/changes
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the
Jody Garnett wrote:
What bothers me more is how changes to geoapi have been handled
recently. In some cases ( like Ben's proposed changes ) it seems a
formal proposal is needed.
I missed this conversation about Ben's proposed changes; what are they?
I was not signed up to the
Justin Deoliveira wrote:
I missed this conversation about Ben's proposed changes; what are
they? I was not signed up to the mailing list for a bit - in general
Ben has my full support since he is deep in the depths of
implementation now and I want to know what is holding him up as soon
as
Justin Deoliveira wrote:
Jody Garnett wrote:
What bothers me more is how changes to geoapi have been handled
recently. In some cases ( like Ben's proposed changes ) it seems a
formal proposal is needed.
I missed this conversation about Ben's proposed changes; what are they?
I
Rob Atkinson wrote:
(warning - rhetorical question) Why do we want a SimpleFeature at all?
In my view, simple feature types exist to support the easy construction
of types from unstructured data such as database views and shapefiles.
They allow, at runtime, decisions such as: can this type be
Jody Garnett wrote:
On a related note Ben; when thinking about the SimpleFeature interface please
understand that it does not meet the needs of GML SimpleFeature profile (it
has reduced scope and is really focused on meeting the basic/shapefile idea
of a Feature).
I am well aware of this.
Andrea Aime wrote:
jgarnett++
I think you mean ++jgarnett, because you want to increment before use. :-)
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Andrea Aime wrote:
SetNames getProperties gives up namespace support,
[...]
ListNames would give the best of both worlds it seems?
These are all interfaces. I thought iteration order was specified by the
implementation? CollectionName is iterable and allows implementers to
choose. See, for
Build broken on Windows: unit test failure in imagemosaic-jdbc
--
Key: GEOT-2364
URL: http://jira.codehaus.org/browse/GEOT-2364
Project: GeoTools
Issue Type: Bug
It is more that iterator order is not defined unless you are a list. So
while we could use SetName (presumably to indicate that we are not going
to have duplicate names) it would fail to capture the idea of an order.
SortedSet would capture the idea of an order (but is otherwise crazy since
the
ok - I resurrected the mappane-use demo. Ian's MapViewer class just
needed a few import / class name changes and it now builds ok. The
intro demo builds now too.
Meanwhile labelling of features (e.g. with countries.shp in the
mappane-use/data dir) will not work properly right now. I've
I am not blocked, just trying to improve the code base. The change I
advocate will need a proposal because it will break everything that uses
a ComplexType, gets its value, and expects a Collection of Property.
And what exactly is that? As far as I know the community schema stuff
you are
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1429/changes
--
started
Updating http://svn.osgeo.org/geotools/trunk
ERROR: Failed to update http://svn.osgeo.org/geotools/trunk
org.tmatesoft.svn.core.SVNException: svn: Failed to add directory
Thanks Michael; the Hudson build is still down until it does a fresh
checkout (since it cannot checkout over top of its old demo/mappane-uses
folder). I hope someone does not need to go into that server and fix it? Is
there an svn update flag that will remove folders?
I did a couple quick reviews
Hi Jody,
Thanks for catching the Envelope usage - much better.
Yep - I was unsure about class names. On the one hand they are
inconveniently long. On the other that means they get grouped
together in the javadocs when you're using the 'All classes' listing
(as I generally do). I don't feel
36 matches
Mail list logo
