Cool, deal :)
Christian Müller wrote:
> Afaik there is nothing to be updated. The imagemosic-jdbc.jar is
> completely in the geotools-2.6.x trunk, the feature-pregen has only 2
> classes in geoserver, one of them deprecated.
> I would propose that you make the move, that is surely faster and
>
Afaik there is nothing to be updated. The imagemosic-jdbc.jar is completely
in the geotools-2.6.x trunk, the feature-pregen has only 2 classes in
geoserver, one of them deprecated.
I would propose that you make the move, that is surely faster and without
the risk of errors, afterwards i will
Hi Christian,
Christian Müller wrote:
> Yep, I am active again, warm up is over.
Hope you enjoyed yourself :)
>
> I can try to port the 2 extensions (imagemosiac-jdbc should work exactly
> like jdbc-db2, feature-pregen has an addational geoserver specific jar
> file).
>
> But until know, I n
Yep, I am active again, warm up is over.
I can try to port the 2 extensions (imagemosiac-jdbc should work exactly
like jdbc-db2, feature-pregen has an addational geoserver specific jar
file).
But until know, I never succeeded in adding an extension perfectly :-(.
Remember the imagemosiac-jdb
Hi Christian,
Based on commit logs and email traffic I assume you are back from
vacation? Would you be able to comment on porting the feature-pregen and
imagemosaic-jdbc extensions to trunk?
Thanks,
-Justin
Justin Deoliveira wrote:
> Looking at 1.7.x it looks like the following extensions sti
None here, actually prefer it. I just love to see that nice pluggable UI
in action :)
David Winslow wrote:
> All right, I've updated geosearch to use these methods. Barring some
> hand-testing (which hopefully I'll get to later this week) I think it's
> ready to go. However, it occurs to me tha
All right, I've updated geosearch to use these methods. Barring some
hand-testing (which hopefully I'll get to later this week) I think it's
ready to go. However, it occurs to me that there is still the geosearch
configuration panel in the Wicket WMS module. Are there any objections
to moving th
Cool, thanks David.
>
> So, I got this mostly ported and committed (no failing tests, so
> shouldn't cause problems for anyone AFAIK). There are a couple of
> inconsistencies in the catalog API that I'd like to bring up, both
> embodied by modifications I had to make in the tests for the module:
On Mon, 2009-07-27 at 14:42 -0400, Justin Deoliveira wrote:
> David Winslow wrote:
> > On Mon, 2009-07-27 at 13:44 -0400, Justin Deoliveira wrote:
> >> geosearch should be easy to port now that the rest stuff is all good
> >> to
> >> go on trunk. David, any chance you will have some time for this
David Winslow wrote:
> On Mon, 2009-07-27 at 13:44 -0400, Justin Deoliveira wrote:
>> geosearch should be easy to port now that the rest stuff is all good
>> to
>> go on trunk. David, any chance you will have some time for this coming
>> up?
>
> Yes, I can take care of this. It looks like I'll b
On Mon, 2009-07-27 at 13:44 -0400, Justin Deoliveira wrote:
> geosearch should be easy to port now that the rest stuff is all good
> to
> go on trunk. David, any chance you will have some time for this coming
> up?
Yes, I can take care of this. It looks like I'll be able to take care
of this bef
Looking at 1.7.x it looks like the following extensions still need to be
ported to trunk:
feature-pregeneralized
imagemosaic-jdbc
geosearch
sqlserver
feature-pregen and imagemosaic-jdbc fall under Christian. I am not sure
what the effort is involved in forward porting them. And I believe
Chris
12 matches
Mail list logo
