Checking on GvSIG CE svn, Sextante
* the main library (sextante.jar) depends on jts 1.12
* The other Sextante libraries (sextante-gui.jar, libMath.jar and
Sextante-algorithms.jar) don't seem to have depency to jts
2018-03-12 0:15 GMT+01:00 :
> On 3/11/2018 23:40, Michaël Michaud wrote:
> >>
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 t
Le 11/03/2018 à 20:25, edgar.sol...@web.de a écrit :
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
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 wit
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 jts
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,
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 :
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 cou
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 th
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 -
A gentle reminder, that t
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 n
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 capaci
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 to migrate to jts 1.15 and jav
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 will
Hi Jumpers,
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 ?
I think we can start this migration on the trunk, and if something need
o be fixed on OpenJUMP 1.12
15 matches
Mail list logo
