Martin Desruisseaux ha scritto:
> Could it be that the trouble in building Geoserver against Geotools-trunk is 
> partially caused by ourself not following our "API change" policy with enough 
> discipline? I saw some public methods where the signature was changed instead 
> of 
> adding a new method and deprecating the old one. It also seem to me that the 
> proposal to add a "@since 2.4" javadoc tag to every new API is not widely 
> applied. So how a Geoserver developper is expected to know which API is 
> stable 
> and which API may fluctuate because not yet commited in a release?

Hum. Since Geoserver is the driver for all changes occurring in 2.4 this
is not the case, that is, geoserver developer are doing the changes most
or the time (but all of the time, and not all geoserver developers are
working against trunk, I'm not for example).

Yet, I agree with you the API change policy should be followed more 
closely, Geoserver may be the driver but as a library we should care of
every possible user.

Yet, I don't quite find "API change" policy on our developers guide...
There is a reference here: 
http://docs.codehaus.org/display/GEOT/Making+a+major+API+shift
but seems to be outdated compared to what you're referring to.

I guess you're referring to Sun's way of doing things, is it documented
anywhere? Or is it just:
* mark operations as deprecated for one release before removing;
* mark release an API has been introduced into using @since
* make sure interfaces do not change over time (something we may not
   be able to follow in practice, and we haven't followed so far either)

Cheers
Andrea

-------------------------------------------------------------------------
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

Reply via email to