GeoTools: Finish up Parameter Interaction discussion and get on to coding
GeoServer: SOS
GeoTools Feature Collection Hacking
Progress:
API change and Javadoc clarified
Massive number of API changes
The story for “add” is fairly easy, change to DefaultFeatureCollection (implements FeatureCollection, Collection so add is present)
uDig did not have that many errors; everyone has steered clear of the add/remove methods etc…
This one sounds more scary then it is - intended to say massive number of downstream classes to fix - but the code is happy for the most part.
Micheal Bedward pointed out that the use of “add” is common in examples and when staging content - DefaultFeatureCollection works in this case as a drop in replacement.
On 2 October 2012 08:22, Jody Garnett <jody.garnett@anonymised.com> wrote:
Micheal Bedward pointed out that the use of "add" is common in examples and
when staging content - DefaultFeatureCollection works in this case as a drop
in replacement.
Someone mention my name ?
You know, I actually think it's confusing for users to be told firstly
that FeatureCollection.add is deprecated, and then that it's cool to
use the add method of DefaultFeatureCollection. At least, it confuses
me, which is why I edited the feature tutorial to use a List to
accumulate features and then wrap that in a ListFeatureCollection.
But I've been bad at keeping up with recent work so am probably
missing something here...
Progress:
a) JUnit 4 - check
b) Resue setup classes
c) Evil order dependent tests
d) Massive amount of changes
Outstanding:
Issues on windows; open readers (poor Alessio)
Backport to 2.2.x (soon rather then have the diff go out of date)
Ideas:
Set up a windows 64bit build server? GeoSolutions has a license - are they brave enough
Next releases
2.2.1 in 3 weeks (who does it? Jody is busy, Andrea and Justin did the last two)
Prepare timetable for the whole 2.2.x series
Just a note that since we don’t maintain a “release branch” anymore (just pushing up a tag from a temporary local branch instead) the last issue i know of should be resolved. During the last release everything went smoothly so i am hoping that the release scripts have been sufficiently hardened. But we’ll see
GeoTools Feature Collection Hacking
Progress:
API change and Javadoc clarified
Massive number of API changes
The story for “add” is fairly easy, change to DefaultFeatureCollection (implements FeatureCollection, Collection so add is present)
uDig did not have that many errors; everyone has steered clear of the add/remove methods etc…
main
JG: Community - skipped as community module is a sandbox, any work going lives undergoes review