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 alas 
they all had major drawbacks.

> For JTS 2.0 we are looking at having multiple geometry APIs (SFSQL, SQL/MM) 
> backing onto the same operations.  With that architecture you *could* produce 
> a module with the old package, but you still would be stuck releasing with 
> respect to have package naming conventions - because we are not vivid 
> solutions.com <http://solutions.com> ...

see your reason why, but that still does not help us or other projects ;(.. 
maybe jigsaw comes to help eventually. as far as i read package names are not 
necessarily static there anymore and can be reassigned.

we will see.. regards ede

> --
> Jody Garnett
> 
> 
> On Mon, 14 May 2018 at 11:00, <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>     Jody,
> 
>     did you send the mail to "[email protected] 
> <mailto:[email protected]>"? 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 repo. for upgrading to jts 1.15 we 
> would need to touch all of these, which i currently do not see happening 
> because of time restraints.
>     it would have been much easier if you simply had kept the package name.
>     so far, Michael and me have decided to wait and see how other projects 
> facing the same challenge are going to deal with it.
> 
>     if push comes to shove, because some new feature is needed, my current 
> backup plan is to simply recompile jts 1.15 with the old package name and 
> include that, which is probably easier than setting up and 
> modifying/compiling all our 3rd party code.
> 
>     ..ede/OJ
> 
>     PS: yeah the java module hell confuses me as well, especially when i see 
> how fast java is developing these days. i am not sure that porting teh 
> existing OJ into modules is going to be seamlessly.
> 
>     [1] https://sourceforge.net/projects/jump-pilot/lists/jump-pilot-devel
> 
>     On 14.05.2018 16:03, Stefan Steiniger wrote:
>     > 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 status is now also only to be a "listener")
>     >
>     > cheers,
>     > Stefan
>     >
>     > On 5/13/18 02:51, Jody Garnett wrote:
>     >> The package names changed. There are upgrade 
> <https://github.com/locationtech/jts/blob/master/MIGRATION.md> instructions 
> with the sed command to run.
>     >>
>     >> * https://github.com/locationtech/jts/releases/tag/jts-1.15.0
>     >>
>     >> I am also interested in the your experience bring Java 10 ready, I am 
> a bit intimidated on the use of "jigsaw" module system.
>     >> On Sat, May 12, 2018 at 1:05 PM Landon Blake 
> <[email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>>> 
> wrote:
>     >>
>     >>     Hi Jody. I'm not involved much in OpenJUMP development anymore, 
> but I see you haven't got a response from the team yet.
>     >>
>     >>     Are there any major breaking changes in JTS 1.15 we would need to 
> worry about? If not, I can try to get a build of OpenJUMP working with JTS 
> 1.15 next week.
>     >>
>     >>     Landon
>     >>     ᐧ
>     >>
>     >>     On Fri, May 11, 2018 at 4:13 PM, Jody Garnett 
> <[email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>>> wrote:
>     >>
>     >>         Congrats on your recent OpenJUMP 1.13 release :)
>     >>
>     >>         I noticed you are still using JTS 1.14, we are planning the 
> JTS roadmap and would like to ask if you would consider upgrading at this 
> time?
>     >>
>     >>         At the FOSS4GNA code sprint we are helping projects upgrade to 
> JTS 1.15 and are in position to issue a dot release if there are any 
> regressions you need to address.
>     >>         --
>     >>         Jody Garnett
>     >>
>     >>
>     >>
>     >>
>     >>     --
>     >>     Landon
>     >>     "Homemade cookies. Mmmmmmmmmmm!"
>     >>
>     >>     Web: www.landonblake.com <http://www.landonblake.com> 
> <http://www.landonblake.com>
>     >>
>     >>     LinkedIn: https://www.linkedin.com/in/landonblake
>     >>
>     >>     Google+: https://plus.google.com/u/0/+LandonBlake
>     >>
>     >>     Facebook: https://www.facebook.com/ScottLandonBlake 
> <https://www.facebook.com/scott.l.blake.3>
>     >>
>     >>     Pinterest: https://www.pinterest.com/landon_blake/
>     >>
>     >
>     >
>     >
>     > 
> ------------------------------------------------------------------------------
>     > 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
>     > [email protected] 
> <mailto:[email protected]>
>     > 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to