https://osgeo-org.atlassian.net/browse/GEOT-5954
Discussion in GeoTools list about migrating. There is an interesting note
about Jai-ext depency on Jts
2018-04-03 17:28 GMT+02:00 Michaël Michaud <m.michael.mich...@orange.fr>:
> Hi,
>
> I can't think of a good solution to migrate without pain.
>
> There is no hurry to migrate and we can probably make one more OJ release
> with JTS 1.14. I'm curious to see how bigger projects like Geotools,
> deegree, hale, udig... will manage this change.
> On the other hand, JTS is one of the biggest strength of OpenJUMP, and
> we'll have to adopt the newer version, sooner or later.
>
> Maybe we should try to communicate a bit more (list, forum , wiki) to know
> what third parties think about this evolution. I think there are no much
> active project using OpenJUMP these days.
>
> Among project derived from OpenJUMP, I can just see Manuela (sourceforge)
> which is still in sync with OpenJUMP. Other projects like Kosmo,
> Adb-Toolbox, SkyJUMP, PirolJUMP seem to have been inactive for four years
> or more.
>
> There has been some interesting plugins since then like an OSM Map reader
> (github, 2017), a LogisticTools PlugIn (github, 2017) and a drillgis plugin
> (github, 2015). But this is not much.
>
> Michaël
>
>
>
> Le 03/04/2018 à 14:51, edgar.sol...@web.de a écrit :
>
>> On 03.04.2018 14:12, Giuseppe Aruta wrote:
>>
>>> It sounds like a lot of job for OpenJUMP.
>>>
>> it will be, for us as well as for all the other jts implementing
>> projects. it would be really interesting, if there is a kind of - we will
>> stick to the old, it's stable enough - attitude out there.
>>
>> What about to write to LocationTech and show the difficulties for such
>>> changes? Is Martin Davis still involved into the JTS project?
>>>
>> the main problem isn't the adaptation, that's mainly replacing package
>> names in imports and changing some moved classes or API incompatibilities.
>>
>> the problem for us, apart from a man power that is virtually not existing
>> for non essential tasks is:
>>
>> we have third party extensions, partly without the sources at hand.
>>
>> all these have to be adapted, compiled, zipped in a jar, just because jts
>> decided it was change the package name, without any major incompatibility
>> in the API itself.
>>
>> ..ede
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
