Andrea Aime a écrit :
> Brent Owens ha scritto:
>> I thought this was already discussed and voted down? 
>> Actual changes before this event will be lost in the formatting 
>> changes, and that was the main reason for no auto-formatting. 
> 
> What? No, exactly the opposite.

I can understand both point of views. It could also be argued that the 
formatting problem would not 
occurs if the jaloppy formatting were not applied automatically. But I realize 
that this argument 
may be more difficult to hold as the number of developpers in the projet 
increase.

I agree about using a uniform coding convention, and my understanding is that 
we agreed a while ago 
on Sun's coding conventions (is that right?). If some parts of my code violate 
the Sun's coding 
convention, those violations need to be fixed. However, last time I tried 
jaloppy, I found that the 
damages (in term of making code harder to read, like breaking alignments) was 
wider than the fixes. 
I realize that I should install jaloppy in my IDE and experiment it more 
extensively. It will be 
difficult for me to do that before October however (after the OGC meeting - I 
guess that I'm going 
to be quite busy in the weeks before the meeting).

In the specific case of the coverage branch merge, I just asked (and obtained) 
8 vacation days 
today. I'm taking vacation (for development work actually) from June 21 to July 
2. Note however that 
I will have to share my time between the coverage branch merge and JSR-275 
(javax.units 
specification), which is in urgent need for care if we don't want Sun to 
withdrawn it like the old 
JSR-108 (by the way, if anyone wish to comment on the very early and partial 
draft posted on 
https://jsr-275.dev.java.net/servlets/ProjectDocumentList?folderID=5344 , that 
would be appreciated).

So I'm ready to start the merge for the "referencing" and "coverage" modules 
tomorrow. Simone, would 
it be right for you?

        Regards,

                Martin.


_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to