MetadataStandard history

Click on the commit message for inspecting the diff and how the code has been rewritten.

Command line:

svn log -r31996:1 https://svn.osgeo.org/geotools/trunk/modules/library/metadata/src/main/java/org/geotools/metadata/MetadataStandard.java
Rev. Date Author Message
306402008-06-12acusterCopyright headers: lib/metadata, this time with feeling (and the el in Toolkit)
305472008-06-06desruisseauxAdded a few MetadataStandard constants. Make the error message slightly more explicit when there is no setter for a given property.
305192008-06-05acusterMetadata header cleanup and copyright review.
302582008-05-08acusterReshuffle the top level repo: drop uDig, move up trunk, tags, and branches.
302572008-05-08acusterMove trunk/gt/ directory contents up to trunk/ and drop gt
289222008-01-24acusterBump the (at)since version to 2.5 since WKTParser was cut from 2.4
285402007-12-29acusterHide buttons which are not yet used
282522007-12-04desruisseauxMore MosaicImageReader work. As a side effect, moved Utilities.getShort[Class]Name in a separated utilities class named 'Classes'. Also added a couple of @Override annotations.
282372007-12-03desruisseauxFixed the search for implemented interfaces (looks deeper in the hierarchy).
280512007-11-26desruisseauxMore Java 5 parameterized types. Include a fix for GEOT-1599 (CitationImpl.getIdentifiers() should returns a set of Identifiers, not a set of Strings).
278642007-11-12desruisseauxUse more Java 5 features. Also fixed a test which failed randomly.
251752007-04-16desruisseauxRemoved 'equals', 'hashCode', 'toString' and 'freeze' methods from every metadata implementation. They are now implemented by generic methods inherited from AbstractMetadata, which perform their work using Java reflection. This way we avoid lot of redundancy, some errors introduced by maintenance ('equals' method not updated in the way they should), more systematic implementations (espcially for the 'toString' method, which was not implemented at all for a majority of metadata), more support for future introduction of other metadata standards than ISO 19115, etc. The cost is more runtime overhead, but it still possible to provide custom implementations for 'equals' and 'hashCode' only in the class that appear to be bottleneck, if we want.
251572007-04-12desruisseauxMetadata review. Also provided a first draft of support classes for new 'equals(...)' copy constructor implementations backed by Java reflection.