Hi Martin,

Sounds like you are making good progress. That said I would like to see 
a formal proposal with voting before any changes come back to geotools. 
Unfortunately the forking nature of how this work has been done 
represents a lot of risk to projects that depend critically on the 
geotools referencing code.

I also think we need it to be easy to revert back to the current 
referencing code. While I realize you have worked hard to maintain most 
of the api and backward compatibility there will undoubtedly be 
regressions. Those regressions could be "deal breakers" so depending 
projects need a way to fall back onto the old code easily.

-Justin

Martin Desruisseaux wrote:
> Hello all
> 
> Following on the JAI operation discussion, I mentioned that I'm working on 
> Operation2D / OperationJAI right now. Actually I'm porting them to geotidy. 
> In 
> the process I rewrote yesterday the way the result of GridCoverage2D 
> operations 
> can be cached (I realised that the implementation in GeoTools 2 is broken). 
> But 
> as far as Operation2D / OperationJAI are concerned, I do not envision API 
> change 
> at this time.
> 
> This bring the question about when geotidy can be offered for a merge with 
> GeoTools. Currently the referencing module is done, except for Oracle and 
> HSQL 
> plugins of EPSG (I'm doing my test on PostgreSQL for now) and the builder 
> package, maybe to move in an other module.
> 
> I'm porting key classes from the coverage module right now (not all of them - 
> I 
> will delay some of them to a later time). GridCoverage2D is alreay ported; 
> the 
> main class left are Operation2D and OperationJAI, which I'm doing today.
> 
> We already have a Mercurial clone of GeoTools SVN: 
> http://hg.geomatys.com/geotools/trunk/. Later this week or at the beging of 
> next 
> week, we will create a clone of this clone in which we will delete the 
> following 
> modules:
> 
>    * metadata
>    * referencing
>    * referencing3D
>    * epsg-*
>    * coverage
>    * coverageio
>    * widgets-swing
>    * widgets-swing-pending
>    * openoffice
> 
> and replace them by dependencies toward geotidy modules. At this stage the 
> goal 
> will be to get GeoTools to compile and pass its tests, without consideration 
> for 
> Java 5. Only after that point, we will downgrate geotidy to Java 5 on a 
> "geotidy 
> for geotools" clone (or something like that). At this point the work will be 
> ready for offering to the community. If accepted, we can merge to SVN the 
> changes applied on the GeoTools Mercurial clone. The "geotidy for geotools" 
> code 
> can be merged to the SVN, or we can left it on Mercurial. I would recommand 
> the 
> later (Mercurial commands look like a lot SVN commands); anyone in the 
> community 
> can take the initiative to declare his Mercurial clone as the "official" one 
> for 
> GeoTools, with agreement of the others.
> 
> The space for the Mercurial clones is already in place:
> 
>      http://hg.geomatys.com/
> 
> Just a note in order to avoid diplomatic incident: the name "geomessy" 
> applies 
> to *our* (at geomatys) code, not to GeoTools code. The comment said "Modules 
> *for* GeoTools", not "Modules *from* GeoTools".
> 
>       Regards,
> 
>               Martin
> 
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Geotools-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel


-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to