On 14.05.2018 18:36, Jody Garnett wrote:
> That does sound like a lot of work.
jupp
> If you have to you could consider doing something with dynamic proxies,
> although I suppose the class based design will prevent that.
i tried. also custom class loading. even considered bytecode patching, but
Hi,
The discussion about JTS 1.15 upgrade is mostly under title ”OpenJUMP next
version”
https://sourceforge.net/p/jump-pilot/mailman/jump-pilot-devel/thread/6c439dc6-366a-9cd3-cd48-4346566fdb6c%40orange.fr/#msg36249751
Knowing our developer resources (Ede, Michaël and Peppe) it feels unlikely t
Jody,
did you send the mail to "jump-pilot-devel@lists.sourceforge.net"? didn't see
it there. maybe just (re)subscribe [1] and disable mail retrieval, so you can
post to it (agn)?
wrt. jts 1.15 - as you might know, we have a lot of extensions, that are not
readily available in our source code
Hi Jody,
as far as I understood Ede and Michaël have looked into creating a
wrapper to accommodate for the package name changes without breaking
stuff; but they better tell you in person (so I cc to the JPP dev list).
I guess any help is appreciated here from OpenJUMP side!
(btw. my personal
