Re: [JPP-Devel] OpenJUMP next version

On 3/11/2018 19:54, Michaël Michaud wrote: > > > Le 11/03/2018 à 18:07, edgar.sol...@web.de a écrit : >> On 3/11/2018 17:45, Michaël Michaud wrote: >>> Migrating to jts 1.15 will probably break a lot of plugins. How do you >>> think we should manage this migration ? >> preferably

Re: [JPP-Devel] OpenJUMP next version

Le 11/03/2018 à 18:07, edgar.sol...@web.de a écrit : On 3/11/2018 17:45, Michaël Michaud wrote: Migrating to jts 1.15 will probably break a lot of plugins. How do you think we should manage this migration ? preferably with a compatibility layer, eg. two classloaders, one w/ old, one new

Re: [JPP-Devel] OpenJUMP next version

On 3/11/2018 23:40, Michaël Michaud wrote: >> now thinking up a routine that takes over most if the src code creation. >> something hackish iterating over the jts sources and creating the above >> mentioned sources that then will need some finetuning only hopefully. > This solution looks better

Re: [JPP-Devel] OpenJUMP next version

Ede, Le 11/03/2018 à 17:20, edgar.sol...@web.de a écrit : On 3/11/2018 17:14, Michaël Michaud wrote: Hi, Le 11/03/2018 à 13:36, edgar.sol...@web.de a écrit : hey Mike, On 3/11/2018 8:21, Michaël Michaud wrote: Hi Jumpers, One of the next big step will be to migrate to jts 1.15 let's do

Re: [JPP-Devel] OpenJUMP next version

On 3/11/2018 17:45, Michaël Michaud wrote: > Migrating to jts 1.15 will probably break a lot of plugins. How do you > think we should manage this migration ? preferably with a compatibility layer, eg. two classloaders, one w/ old, one new jts. or standin JTS classes in OJ core,

Re: [JPP-Devel] OpenJUMP next version

Hi, Le 11/03/2018 à 13:36, edgar.sol...@web.de a écrit : hey Mike, On 3/11/2018 8:21, Michaël Michaud wrote: Hi Jumpers, One of the next big step will be to migrate to jts 1.15 let's do those as usual in trunk OK, we just need to anticipate consequences as we'll probably not have the

Re: [JPP-Devel] OpenJUMP next version

With respect to the branching issue... It may be a silly idea, but how about migrating to and importing to github - as a solution? The last stable version will then be on SVN and work with the new JTS will be on Github. So the SVN version is always intact/a back-up for later on. But of

Re: [JPP-Devel] OpenJUMP next version

Hi Brian, Thanks for the reminder. Let us know when the ubuntu/java version will be decided. Anyway, the recent OpenJUMP 1.12 is compatible with java 7, so that an upgrade of OpenJUMP in the next OSGeoLive should be possible anyway. Michaël Le 11/03/2018 à 17:21, Brian M Hamlin a écrit :

Re: [JPP-Devel] OpenJUMP next version

Hi Michaël, I don't have the experience about it Nevertheless I feel that the first your proposal is more easy to manage, as we are a small comunity of developers. Peppe 2018-03-11 8:21 GMT+01:00 Michaël Michaud : > Hi Jumpers, > > One of the next big step will be

Re: [JPP-Devel] OpenJUMP next version

On Sun, 11 Mar 2018 08:21:42 0100, Michaël Michaud wrote:    One of the next big step will be to migrate to jts 1.15 and java 1.8.    Migrating to jts 1.15 will probably break a lot of plugins. How do you       think we should manage this migration ? - Hello All -

Re: [JPP-Devel] OpenJUMP next version

hey Mike, On 3/11/2018 8:21, Michaël Michaud wrote: > Hi Jumpers, > > One of the next big step will be to migrate to jts 1.15 let's do those as usual in trunk >and java 1.8. same here, currently i see no incompatibilities. what changes do you propose exactly? > > Migrating to jts 1.15

Re: [JPP-Devel] OpenJUMP next version

On 3/11/2018 17:14, Michaël Michaud wrote: > Hi, > > Le 11/03/2018 à 13:36, edgar.sol...@web.de a écrit : >> hey Mike, >> >> On 3/11/2018 8:21, Michaël Michaud wrote: >>> Hi Jumpers, >>> >>> One of the next big step will be to migrate to jts 1.15 >> let's do those as usual in trunk > OK, we just