Quick meeting - 20mins short
jgarnett Morning - hey we going to have a meeting today?
=-= jgarnett has changed the topic to "2.2.M1 is released on an unsuspectng public, what is next? IRC Meeting ... now!"
rschulz sure, I have nothing to discuss though
jgarnett That is okay, there are enough questions around we should be able to have a meeting - at least for justin and geoserver/geotools contact.
CIA-6 rgould 1.0.x * r16630 udig/plugins/ (113 files in 3 dirs): exported developer's guide
jgarnett So guys what is happening? Anyone have something needing doing, or agenda topics?
jdeolive hello all
jdeolive 1) catalog api onto trunk
jgarnett Hi justin - just made the call for topics ...
jgarnett 2) 2.2.M2
jgarnett Justin did you have time to go through the changes that will need to be made to factory for your container stuff?
jgarnett Or are you going to save that for a emergency basis, aka when you need to do it...
jdeolive the latter
jgarnett k
jdeolive i have been stuck doing bug fixes, when i have free time i have been doing the container research
jgarnett Other than that lets just have a short meeting, and be done.
jdeolive given some time, and some motivation, i can start looking at it, it would be nice if someone had a use case
jdeolive cool
jgarnett Better to keep lines of communication open then skip the IRC entirely.
jdeolive agreed
jgarnett Well we have our use case, a GeometryFactory that decimates.
jgarnett Okay 1. over to you justin ...
jdeolive so the plan is to throw the catalog interfaces / abstract classes into main, under the existing catalog pagckages
jdeolive and throw all the implementations to the existing plugins
jdeolive and that is about it
jdeolive jody, you said you made some changes, i will have to merge at some point
jdeolive it would also be nice if the udig catalog merged over to the geotools catalog, however not sure when you guys will be ready for that
jgarnett Jesse - what do you think?
jgarnett We are on trunk so there is not a technical problem ...
jgarnett Oh other agenda item 3) Intro for the newly voted in - Justin/Mark
Jesse_eichar I think I'm ok with it.
Jesse_eichar (catalog merge)
jgarnett I would like to see the code reduction, question is if it gets done for UDIG 1.1 or not, since it is a formal API change I would like to see it done ...
jgarnett Lets answer that next week justin, after we have time to get our heads straightened around here.
jgarnett Skipping ahread to 3.
jdeolive no problem
jgarnett Justin and Mark - you are module maintainers now
jgarnett that means you get to vote. Aka please vote. GeoTools is actually run my module maintainers - PMC is reserved for hapless volunteers that do things like make builds for the community.
CIA-6 rgould * r16631 udig/plugins/ (113 files in 3 dirs): exported developer's guide
jdeolive i was before as well
jgarnett This project is all about the code, and code = module maintainers.
jdeolive i am fine with that
jgarnett Anything else - or shall we vote on the catalog API to trunk change?
jgarnett +1 - sounds great!
jdeolive nope that is it
jdeolive +1
Jesse_eichar +1 if just talks to me about the 1 outstanding problem with catalog
Jesse_eichar just=justin
jgarnett Hi richard - we are voting on the catalog API
jgarnett I already mentioned the GeoResource's needing children.
jdeolive yeah, how large was the change
rgould I haven't been following the lists. uDig's catalog API is being moved into GeoTools?
jdeolive i need to merge it in
jgarnett Jesse was thinking two handles referencing the same literal content... basically the fact that resolving handles needs to hit an extention point/mechanism...
jgarnett Implmentation issue rather then API issue.
jgarnett Next topic 2.2.M2
jgarnett chorner - are your aggregate changes ready for release? We aleady had a main split occur while we waited.
chorner sure
jgarnett Cool - I am tempted to split the API out of main as well (aka planned change, but I was waiting for the next release). If this release already has a main split ....
jgarnett ... does anyone have any thoughts on this stuff?
jdeolive on the main split?
jgarnett well adding to it, splitting out the interfaces
jdeolive I think the more that gets taken out of main the better
jgarnett so module/main (is all impls) module/api (all interfaces) module/coverage (coverge impls) module/referencing (geoapi impls)
jgarnett For a while we had a mechaism to merge them all back together ... it suxed in the pre GeoTools 2.0 days when main consisted of 8 different things.
jdeolive ideally i would like to the catalog api be its own beast too, but there is already space in main for it
jgarnett Could be maven 2 will help with that ...
jgarnett jdeolive - there should not be a need, catalog 2 impl is very small - just enough to let the plugin system function. Indeed all of main should behave the same way ...
jgarnett Justin have you tried maven 2?
jdeolive sure its small, so if someone wants to use just it, they have to take all of main along for the ride
jdeolive yes
jgarnett Martin started but is now on holiday ... I am going to make this release using maven 1
jdeolive my experience is good and bad
jdeolive the good is that project descriptors are much shorter, and the transitive dependencies are nice
jdeolive however
jgarnett Interesting - all of main is smaller every passing second.
jdeolive i find the actuall building to be unstable
jdeolive it seems to want to download dependencies that dont exist
jdeolive and it appears to happen at random
jdeolive and alot of the plugins arent as mature
jdeolive for instance
jdeolive the web archive plugins (war), i couldn't get it to work
jdeolive and with maven 1.x it works right out of the box
jgarnett Aside: geotools build just failed: Error retrieving artifact from [http://ibiblio.org/maven/gt2/jars/coverage-2.2.x.jar
jgarnett (connection timed out)
jdeolive appears an online test is killing the build perhaps?
jgarnett Well I do hope maven 2 will be ready at some point, should we check back in a couple months? Any idea what their release timeline is like?
jdeolive nope, but i think that might be a good idea, it did take maven 1 to point releases to get rock solid
jdeolive to = 2
jgarnett Well that may be it for the meeting, anything else or should I kick out the logs?
jgarnett I am glad we got the domain back
jgarnett We do have trouble on the users lists, more people wanting styledmapviewer to work. And misleading documentation.
jgarnett Tempted to remove the docs since nobody is working on the code, or answering email.
jgarnett Okay guys, thanks for amusing me with a meeting.
=-= jgarnett has changed the topic to "This week in GeoTools 2.2.M2 and Catalog APIs merge."
jdeolive ciao
rschulz jody, is the "current state of geotools map viewers" doc someone wrote (I forget who) on the wiki?
rschulz It might help remove some of the confusion
jgarnett I don't think the dude posted it ...
jgarnett adrian.
jgarnett Can you ask on the list for us?
rschulz yes, I will write a note to myself to bug him tonight
rschulz ok, note written
jgarnett cool
rschulz bye