Skip to main content

[jsr363-experts] Re: Feature Freeze before Final Draft

  • From: Martin Desruisseaux < >
  • To:
  • Subject: [jsr363-experts] Re: Feature Freeze before Final Draft
  • Date: Sat, 1 Oct 2016 01:02:19 +0200
  • Organization: Geomatys

Hello Werner

Le 30/09/16 à 13:33, Werner Keil a écrit :
> Hard to say from the stats, if those download numbers come from Apache
> SIS or Eclipse projects like uDig, some using SIS, others GeoAPI or
> even JScience directly. If it gradually changes, that's fine.

uDig, GeoTools and GeoServer uses GeoAPI, so in theory they would
migrate. However they created their own fork of GeoAPI (without changing
their package name) and I do not know what are their intention regarding
unit of measurement. The usual attitude of some GeoTools developers is
to ask money for doing anything.

To make a comparison, imagine that a project forked JSR-275 and put the
fork in their own source code repository without changing the package
name, without consideration for the unethical aspect of using a package
they do not own (javax.measure), without synchronization with the
official javax.measure evolution and without consideration for the
trouble that it cause to JSR-363 users. What uDig/GeoTools/GeoServer do
regarding GeoAPI is similar.

    Martin




[jsr363-experts] Re: Feature Freeze before Final Draft

Werner Keil 09/30/2016

[jsr363-experts] Re: Feature Freeze before Final Draft

Martin Desruisseaux 09/30/2016

[jsr363-experts] Re: Feature Freeze before Final Draft

Werner Keil 09/30/2016

[jsr363-experts] Re: Feature Freeze before Final Draft

Martin Desruisseaux 09/30/2016
 
 
Close
loading
Please Confirm
Close