Changing vote to -1 until R&D branches come home.
Hmm, after thinking more about this I realize that I will probably get
screwed if we go forward with formatting now. I think the gain of having
6 months of work come back home smoothly outweighs the need for
consitency at the moment.
I know that theoretically running jalopy on both branches and then
merging should elliviate most of the issues but I am still hesitant.
-Justin
Jody Garnett wrote:
Martin Desruisseaux wrote:
Cory Horner a écrit :
Martin: +1 (if sun convention)
I'm rather hesitant. I need to try on existing code and see what the
result looks like. I'm more confortable with Dave's position (run
Jaloppy for new code).
Understood, but that does not solve my basic problem - that the
developers guide does not agree with practice.
Since we have a mandate lets triple check the last 2.2.RC and then
format with Jalopy before release. Note this *was* done for 2.0 release
as a way of ensuring the geotools header was up to date.
If the other branches can then Run Jalopy and sync up with the changes
from 2.2.x we should be in a good position to go forward. Justin you are
kinda of out of luck (and will be modifying almost every file anyways) -
I hope that using Jalopy will limit your problems to code, and not
whitespace.
Jody
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
