From: Martin D. <mar...@no...> - 2006-03-26 22:04:47
|
Jody Garnett a =E9crit : > Hi Marting, one of the joys of working on the FM branch is exposure to=20 > the latest GenericName interface - as an example the implementation of=20 > NamedIdentifier "breaks".... is the following patch suitable? > /** > * @since GeoAPI 2.1 > */ > public NameSpace scope() { > return getName().scope(); > } NameSpace is not yet implemented in Geotools, so it will not work neither= . Every GeoAPI interface or method with a "@since 2.1" comment will break G= eotools build. GenericName=20 is not the only one. There is also new methods in CoordinateSystemAxis, C= overage, GridCoverage,=20 Envelope, CRSFactory, etc. A possible patch is to implements empty skeleton for those methods in Geo= API, something like: /** * @since 2.3 */ public NameSpace scope() { // TODO: New GeoAPI 2.1 method throw new UnsupportedOperationException("Not yet implemented."); } I suggest to put "@since 2.3" in the comment instead of "@since GeoAPI 2.= 1" because the @since tag=20 is about the Geotools version when this method were introduced. And the "= // TODO: New GeoAPI 2.1"=20 argument will help me to perform a search in the whole code base on "GeoA= PI 2.1" keyword, for=20 spotting the methods that need to be implemented. Could it work? Martin. |