James Macgill wrote:
2.1 developers other than ensuring that code written against 2.1 would
work on 2.2. (I can well imagine that this is not holding true and if
so needs to be addresed urgently)
I agree - it is not holding true. But 2.2 is broken, if we had performed
some QA checks on 2.1 we
would of founds some of these. I am kind of aghast at the quality gap
here, we need to define equals and hashCode, it was not
tracking SLD 1.0, and the so on ... style is a mess that is just now
starting to improve.
In short I am not sure how we are supposed to proceed when things are in
error?
I have to agree with that, idealy we should all follow the
conventions and use jalopy before commiting code. BUT if that does
not happen DO NOT go refomating other peoples code, there is little
more anoying that tracking down changes when there are none. (Though
diffing with ignore white space switched on can be a life saver!)
I think this was a problem with the styling package - as outlined by
Corey earlier. I do hope it is
formatted with Jalopy now.
Jody
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
