A sloppy weekly meeting: 1) Nothing said against YourKit 2) 2.2.0 good to go (except it doesn't compile right at this instant) 3) 2.2.0 still scheduled to go out after rgould's exams (unless you decide to release before) 4) WFS will be made permissive to incorrect requrests (but with some mumbling)
* cholmes ([EMAIL PROTECTED]) has joined #geotools * gtbot ([EMAIL PROTECTED]) has joined #geotools <chorner> gtbot, add your favorite profiler <gtbot> Added agenda item '1: your favorite profiler' to the list. <chorner> gtbot, add 2.2.0 <gtbot> Added agenda item '2: 2.2.0' to the list. <Jesse_Eichar77> gtbot, add JMapPane <gtbot> Added agenda item '3: JMapPane' to the list. <acuster> gtbot, welcome back! <acuster> gtbot, insult <acuster> nah, you're not a real bot yet. <simboss> gtbot, subversion <simboss> cool <simboss> :P <acuster> a little light reading: http://news.independent.co.uk/world/fisk/article1204432.ece * jdeolive has quit (Read error: 104 (Connection reset by peer)) <acuster> okay, we going to start? <acuster> cholmes, chorner ethangio FrankW Jesse_Eichar77 simboss ? <cholmes> I'm here. <simboss> ready * FrankW is reading about Lebanon... <FrankW> but I'll try to pay attention here too. <acuster> 1) was andrea's idea, seems to have got a good reception * iant_ ([EMAIL PROTECTED]) has joined #geotools <acuster> anyone got something to add? <iant_> hi <acuster> iant_, just starting on (1) <acuster> gtbot, list <gtbot> Agenda Items: <gtbot> 1: your favorite profiler <gtbot> 2: 2.2.0 <gtbot> 3: JMapPane <gtbot> End of agenda items. <acuster> okay on to (2) then <acuster> we are working on getting jmappane working <acuster> the javadocs should be fixed but can only be verified during release <acuster> any other showstoppers? <acuster> there have been some fixes going in <acuster> are they done? <acuster> okay, assuming the resounding silence means 2.2.0 is good to release when anyone can pull it off. <acuster> on to (3) <acuster> Jesse_Eichar77, you wanted to say stuff? * FrankW shouts out some silence. <iant_> ? <iant_> ping? <acuster> okay, anything else? <simboss> Jesse_Eichar77 <simboss> I have a question guys * acuster can pull out the old; ask, don't ask to ask * rgould ([EMAIL PROTECTED]) has joined #geotools <rgould> hi <Jesse_Eichar77> meeting with Paul 1 sec <acuster> go simboss, <simboss> is there any timeline for 2.3? <simboss> I might have forgotten sory <Jesse_Eichar77> ok back * iant_ has quit () <Jesse_Eichar77> simboss: <Jesse_Eichar77> not that I know <simboss> ok <Jesse_Eichar77> I didn't have too much to say about the JMapPane. But I understand there are some issues with it? <Jesse_Eichar77> (Just parroting back what Jody told me) <acuster> JMapPane has been moved into ext/ on the 2.2 branch <simboss> andrea came up with some issues <simboss> he sent out an email <acuster> as well as some extra fluff <simboss> abou ti <simboss> it * iant_ ([EMAIL PROTECTED]) has joined #geotools <acuster> the fluff (filter stuff) will be chopped out <iant_> hi again <Jesse_Eichar77> so nobody is maintaining it? <acuster> the CRSPicker can't be made to work trivially so it will be cut <Jesse_Eichar77> welcome back. <acuster> which leaves us with a nice lean widget <acuster> which is *all* that Geotools should have <Jesse_Eichar77> so who's doing the cutting? <iant_> ping? <acuster> hey iant_ <acuster> you going to work on JMapPane? Do you have time? <iant_> hi - I'm having connection problems <iant_> I'll try to work on it <acuster> Jody was doing some cutting <iant_> I'm still trying to sort my home network after house move <acuster> as far as I'm concerned, it's good enough to ship <Jesse_Eichar77> ok cool <acuster> we don't really care if it's full of bugs <acuster> since it's not really part of geotools <Jesse_Eichar77> :D <iant_> Feel free to all chip in and I'll be module maintainer <acuster> it exists uniquely as a teaching device for others to start with <acuster> and for me to document Geotools <iant_> and also as the most requested feature in 2.2.0 since styledmappane was removed :-) <Jesse_Eichar77> ok. so I missed the bit about 2.2.0 <acuster> yes, but that would indicate that it were a "feature" and it has ceased to be (since it is a convinient time to pass the work on to the users) <Jesse_Eichar77> As far as I know it is ready to go out. <chorner> *almost* <Jesse_Eichar77> do we have anyone to release it? <acuster> gtbot, add javadocs <gtbot> Added agenda item '4: javadocs' to the list. <chorner> i'm adding a couple fixes in the next couple hours, but it is unlikely it will be released before then <chorner> also: the 2.2.x build is broken (ext/go) <acuster> how? * iant_ has quit () <chorner> [INFO] Compilation failure <chorner> c:\java\geotools\2.2.x\ext\go\src\org\geotools\geometry\array \CompressionLevel.java:[112,19] compareTo(java.lang.Object) in org.ge <chorner> otools.geometry.array.CompressionLevel cannot override compareTo(java.lang.Object) in org.opengis.util.CodeList; overridden method <chorner> is final <acuster> rgould, if no one else beats you to it, will you be able to release after your exams? <rgould> acuster, certainly <acuster> cool <Jesse_Eichar77> sweet. <Jesse_Eichar77> richard did you add you agenda item? <Jesse_Eichar77> about wfs capabilities? <rgould> oh <rgould> forgot about that <rgould> gtbot, add Specification Purity <gtbot> Added agenda item '5: Specification Purity' to the list. <acuster> anyone have anything to say on (1) the profiler (2) 2.2.0 or (3) jmappane? <Jesse_Eichar77> Profiler: I like YourKit <Jesse_Eichar77> done <acuster> gtbot, list <gtbot> Agenda Items: <gtbot> 1: your favorite profiler <gtbot> 2: 2.2.0 <gtbot> 3: JMapPane <gtbot> 4: javadocs <gtbot> 5: Specification Purity <gtbot> End of agenda items. <acuster> okay a quick (4) <acuster> i'm writing a stupid example app that tries to cover a lot of the code base, <acuster> as of now there is one (1) import from geoapi <acuster> when you try to learn geotools by studying geoapi, <acuster> you waste a lot of time because it's not at all clear what is relevant and what is not <acuster> Would it be possible, in future releases, to somehow trim down the geoapi released with Geotools <acuster> to contain only the relevant modules? * cholmes has quit (Read error: 104 (Connection reset by peer)) <acuster> I don't expect an answer, but am raising the possibility <acuster> Done <Jesse_Eichar77> A good point that * cholmes ([EMAIL PROTECTED]) has joined #geotools <Jesse_Eichar77> don't have too much of interest to say about it though. <acuster> okay, on to (5) <acuster> rgould? <rgould> ok <rgould> so due to a recent bug issue in uDig, I discovered that the WFS plugin in geotools explodes if it encounters a Capabilities document that does not conform to the WFS specification <rgould> the problem is that the part that was missing from the document was not essential to use the service <rgould> now <rgould> a couple years ago, when I was implementing the WMS plugin, James gasped in dismay as he realized I was permitting servers that did not conform to the WMS specification to be accessed normally <rgould> i would like to do the same to WFS <rgould> (so we can access these broken servers) <FrankW> rgould: ++ on permissiveness. <rgould> I thought it might be a good idea to come up with a general concensus regarding what to do when something breaks specification <rgould> It has been a goal of uDig to communicate with every server out there <rgould> that's pretty much all I have to say <acuster> can you communicate but raise a big red flag? <cholmes> I'm inclined to say that we should shoot some sort of warning when something's not right. <cholmes> yeah, what acuster said. <rgould> that should be easy to do * iant__ ([EMAIL PROTECTED]) has joined #geotools <rgould> and then a client like uDig can look at the flag and perhaps display a message to curious users <acuster> well, it's also making user know that it's not uDig's problem <cholmes> Hopefully even at the udig level - have a red flag that says the user could get in touch with the provider of the service about properly meeting the specification. <acuster> or Geotools' <rgould> right <rgould> heh - OWS services include contact information - uDig could assist in contacting them :) <cholmes> Even better, windows style 'send an error report now' - which would send some canned email. <rgould> yeah <cholmes> Yeah, what rgould said. <acuster> yes, that's exactly the kind of thing that will cover Geotools in the long term <acuster> very nice <acuster> +1 for exapansiveness, if accompanied by a nasty note :-) <rgould> okay, so unless there are objections, i will make WFS permissive and will add a flag to indicate that the server has broken specification (and maybe some messages regarding it to) <rgould> hahaha <acuster> so we are done: open floor for five minutes and then we can close the meeting <acuster> well, that's not going anywhere. <acuster> so we are done. Thanks all <rgould> thanks for running the meeting <FrankW> later <chorner> someone will need to post logs <rgould> gtbot, stop <gtbot> Logging stopped. <gtbot> Posting news to GeoTools confluence... <gtbot> Successfully posted. <rgould> ;) <chorner> i don't remember anyone pressing start <rgould> oh <rgould> you are right <rgould> it is empty ------------------------------------------------------------------------- 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
