Answering a few questions: Andrea Aime: I'm not sure I understood the last part about filters. You mean that you still have to port stuff from FM? Jody Garnett: ah the changes went like this ... Jody Garnett: we updated the GeoAPI Filter interfaces to Filter 1.1 Jody Garnett: and made geotools FM use them Jody Garnett: and then merged that change to geotools trunk Jody Garnett: Then we started in on the feature model Jody Garnett: updating geoapi Jody Garnett: and we have not completed that work nor merged to trunk Jody Garnett: the the point in which justin updated trunk, is where we need to cut a geoapi jar... Jody Garnett: the geoapi jar from trunk has 4 RnD efforts going on. Jody Garnett: 1) filter - done Jody Garnett: 2) FM - not done Jody Garnett: 3) catalog - seems to be stuck not sure who is doing it ... Jody Garnett: 4) coverage changes - not sure if it is done ... Jody Garnett: There is a page where we planned to make branches for those 4 ideas, but nobody has done it yet. Andrea Aime: Erk... too much going on... we can't make trunk depend on that 4 legged beast Jody Garnett: that is why we need to shape up geoapi, I tried - I made the plan and just never got the time to break it up. Jody Garnett: Um I better send this to geoapi list, chances are they do not remember.... it was Febuary.Jody Garnett wrote:
here is the page mentioned: http://docs.codehaus.org/display/GEO/Repository+Organization > Andrea has gradually noticed how messed up geotools trunk is right now > ... and has been sobbing quietly in a little corner window of my desktop > for minuets now (hi Andrea). > > Here is the situation: > - GeoTools 2.2.x works against GeoAPI 2.0 > - GeoTools FM works against GeoAPI 2.1 > - GeoTools trunk is lost in the woods and the wolves are coming... > > I "think" the geoapi jar we are using for trunk is something Justin > cooked up with Eclipse and put up on a wiki so others could compile FM, > and then when the initial Filter changes were merged back onto trunk > this franken jar entered our life. > > Since trunk is finally becoming important, and a target for GeoServer > and uDig development we are going to have to fork a GeoAPI branch, get > it to compile and give it a nice timestamp .... or we are going to have > to catch up with the current GeoAPI snapshot. > > Andrea and Justin if you can please advise, > Jody > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Geoapi-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/geoapi-devel > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
