In the process of hacking geotidy, I'm fixing many JIRA tasks. Following are
fixed on geotidy only:

    GEOT-640:  Avoid (OTHER,EAST,NORTH) axis directions for GeocentricCRS
               when possible
    GEOT-915:  ResourceCompiler should be refactored as a Maven plugin
    GEOT-1100: Deprecate the AbstractFactory.priority field
    GEOT-1217: Allow Formattable objects to be turned into WKT specifying
               both indent and strictness
    GEOT-1517: Split org.geotools.util and its friends in a "util" module
    GEOT-1526: Consider moving GenericName and Record implementations in a
               "naming" package
    GEOT-411   [Abridged] Molodenski transforms should accept 'dim_source'
                and 'dim_target' arguments

Following are patched on geotools 2.5, but got a better fix on geotidy:

    GEOT-2046: MolodenskiTransform fails in some cases when the output
               array overwrites the input array but with an offset
    GEOS-1720: Grid coverage reprojection degrades image quality in an
               unacceptable way


What should I do? Some alternatives are:

1) Resolve (not close) JIRA task as fixed for release 3.0 (or whatever
   release number you wish). I can not commit for GeoTools 2.6 since it
   will depend on the progress of the Java 5 port (I will probably help
   a bit for that).

2) Don't touch the JIRA task and list the fixed tasks in a separated file.

        Martin

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to