As of a few moments ago I have my first "hello world" example working <https://github.com/eclipse/imagen/pull/11> for ImageN.
This is a relicensed copy of the JAI codebase as an open source project. The planning for this is based on our ReplaceJAI <https://github.com/geotools/geotools/wiki/Replace-JAI> technical debt and a bit of hustle from our friends at the Eclipse Foundation putting us in touch with Oracle engineers. While this is something I have been working at in my "spare" time I view it as quite important to the long term health of our GeoTools ecosystem. Indeed I plan to work on it next week at the OSGeo code sprint (along with anyone else willing to join me in person or remotely). To that end I would like to update the "ReplaceJAI" plan and work towards making this change during this release cycle. My rough idea (feedback welcome): 1) ImageN 0.8 - just changing the package names and license (this is a requirement from Oracle Engineering) - priority is to ensure we got all of the codebase and make the best use of Oracle engineers while available 2) ImageN 0.9 - clearly provide migration instructions from JAI codecs to ImageIO for Java 8 and Java 11. - deprecate functionality "we" do not wish to maintain going forward (like RMI remoting). - Introduce key superclasses (such as JAI extends ImageN) while maintaining easy migration path - provides a clear migration path for projects migrating from JAI - folks in JAI-EXT improvements (such as concurrent-tile-cache) directly - setup up "ext" module for JAI-EXT operations 2) ImageN 1.0 - drop any functionality that clearly does not have a stakeholder - target for the GeoTools ecosystem migration Keep in mind this project is going to be used by more than just the GeoTools ecosystem, but if we are doing the work we can help ensure it meets our requirements. -- Jody Garnett
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
