Hi Martin, >> isn't the jdk6 branch sufficient? or shouldn't it be a goal of such a >> branch to be android compatible? > > The Android API is a subset of the JDK6 API. For example the Android > branch would have all JAXB annotations removed (at least for current > Android releases). They were no SQL neither prior Android 4; instead > Google defined its own package for using their embedded SQLite. > > Other example: the referencing module relies extensively on affine > transforms. The JDK branches use java.awt.geom.AffineTransform. But > the Android API excluded the full Java2D API - instead, they define > their own Affine transform class. So the Android branch have to use > the Google flavour of Affine transforms instead than the Java2D one.
Ah, ok I see. In GraphHopper I could handle the Android stuff by putting the dependencies (only logging) together when packaging, so I could avoid a separate branch. In SIS it could be done with sql and jaxb in the same manner but if android has its own probably hardware boosted geometry package that is not an option, I guess. Peter.
