>
> What bothers me more is how changes to geoapi have been handled
> recently. In some cases ( like Ben's proposed changes ) it seems a
> formal proposal is needed.
I missed this conversation about Ben's proposed changes; what are they? I
was not signed up to the mailing list for a bit - in general Ben has my full
support since he is deep in the depths of implementation now and I want to
know what is holding him up as soon as possible.
Ben are you available for comment? What is up here?
> However in the case of recent style changes it seems breaking api is ok. It
> seems ambiguous to me.
You are correct that something was amiss; Johnathan was good about talking
with me about the addition of an ExtensionSymbolizer and we rolled out the
patch in good order; he missed adding the method to StyleFactory which I
found during my review (I believe I rolled out this patch correctly
yesterday). Johanathan then went and changed some of the methods to take a
String rather than an Expression as a parfameter - and I am unclear on if
this was deployed; or automatically deployed resulting in the current
breakage.
I have talked to him; and the geoapi list; and do not plan to see an api
change without talking it over first (hense the email thread with andrea on
this subject).
Jody
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
