The use of the ra_svn module rather than the ra_serf one seems to be a
rather good approach.
The migration process worked well during the last 2 and a half hours. It
already took into account all the branches, and partially the trunk and
the tags from 1.2preC to 1.7.0.
I'll let you know abou
See my inline answers below.
On 14/08/2020 20:38, edgar.sol...@web.de wrote:
some more questions
1. did it ever run through completely?
During my first tests, I used a starting revision number closer to 6242
to test the process and to save some time (as I knew it would take ages
to go throu
some more questions
1. did it ever run through completely?
2. why start at revision 859?
3. did you try https://github.com/nirvdrum/svn2git#debugging ?
it'd probably more stable if you could work with a full local checkout.. ede
On 14.08.2020 21:26, Eric wrote:
> The command is to migrate the c
The command is to migrate the complete project, including its history,
from svn to git:
svn2git https://svn.code.sf.net/p/jump-pilot/code/core --exclude docs
--revision 859:6242 --authors ../authors.txt
I first tried without excluding the docs folder. The revision parameters
match the first an
probably just sf.net's svn acting up. it sometimes throws weird errors that
resolve itself after a time. i guess they get fixed on their servers. who knows.
anyway. what is it you are doing when it errs out? a complete checkout? what
commands are you running? can you give some context?
..ede
O
Hi,
I'm encountering a problem during the local migration (ra_serf: The
server sent a truncated HTTP response body) when I try to do it from
revision 859 to revision 6242.
I tried to exclude the 'docs' folder to reduce the size of it, without
much success (still the same error after an hour
openjump-gis ok for me too
2020-08-14 12:03 GMT+02:00, edgar.sol...@web.de :
> oj-devs
> oj-developers
> oj-team
> or jump instead of oj
>
> so many possibilieits ..ede:))
>
> On 14.08.2020 11:53, Giuseppe Aruta wrote:
>> jump-pilot
>> or
>> openjump-pilot
>> or
>> openjump2
>>
>> 2020-08-14 11:50
oj-devs
oj-developers
oj-team
or jump instead of oj
so many possibilieits ..ede:))
On 14.08.2020 11:53, Giuseppe Aruta wrote:
> jump-pilot
> or
> openjump-pilot
> or
> openjump2
>
> 2020-08-14 11:50 GMT+02:00, Eric :
>> Hi,
>>
>> The GitHub support team answered me this morning, stating that the
jump-pilot
or
openjump-pilot
or
openjump2
2020-08-14 11:50 GMT+02:00, Eric :
> Hi,
>
> The GitHub support team answered me this morning, stating that the
> ownership transfer of the 'openjump' username or organisation is not
> possible at the moment:
>
>> While I'd love to help, I'm afraid we won'
Hi,
The GitHub support team answered me this morning, stating that the
ownership transfer of the 'openjump' username or organisation is not
possible at the moment:
While I'd love to help, I'm afraid we won't be able to release that
username for you today as it's not dormant (not all activity
no worries. i'm pretty sure we are not fixed on that name. for years we have
been known as /jump-pilot/ (anybody know why?) and it worked as well. how about
you work with a private repo in the mean time and we'll deal with name and
organisation when we are ready to branch which is not going to b
Hi all,
Thanks to all of you.
According to your answers, I'm in the process of creating a GitHub
organisation named 'openjump', containing a public repository named
'openjump-migration'. The current problem is that someone created an
account or an organisation with this name last April
(http
*>So for OpenJUMP I would suggest:- openjump for the organisation / group,-
openjump for the main code,- openjump-test for the temporary project we are
talking about here, toavoid any confusion.*
Since Sextante java libraries have the potentiality to be extended to many
other gis projects (the ori
yup indenting is clearly broken in this reply, maybe better not reply inline
with that client Mike ;).. ede
On 12.08.2020 09:17, Michaud Michael wrote:
> Hi,
>
> >>> On 07.08.2020 20:55, Eric wrote:
> Then I checked which OJ lib dependencies rely on JTS and it seems that
> there is only de
Hi,>>> On 07.08.2020 20:55, Eric wrote: Then I checked which OJ lib dependencies rely on JTS and it seems that there is only deegree 2, without considering here the plethora of extensions/plugins.>>> which is the main obstacle. the only clean solution i see is to branch out a new OJ 2.x t
Hi Eric
Open discussion:
*>>- The idea is to create a temporary Git project/repository as Ede
mentioned too. There are two main platforms for that, GitHub and GitLab.
Let me know which one you prefer, knowing that it is possible to have both
solutions, working only on one, with a mirroring for th
Hi Ede,
Thanks. I let the licencing issue aside as it seems to be resolved. See
my inline answers.
On 11/08/2020 12:01, edgar.sol...@web.de wrote:
tl;dr let's wait how the licensing issue (other email) turns out, apart from
that my answers below.
On 10.08.2020 15:42, Eric wrote:
Hi Ede,
T
tl;dr let's wait how the licensing issue (other email) turns out, apart from
that my answers below.
On 10.08.2020 15:42, Eric wrote:
> Hi Ede,
>
> Thanks for your welcome and for your answers. See my inline replies for some
> of them (I deleted the other parts).
>
> On 09/08/2020 16:40, edgar.so
looks unmaintained with last commit being from 2017-05-24
https://sourceforge.net/p/gvsigce/code/HEAD/tree/trunk/sextante/
..ede
On 11.08.2020 08:31, Giuseppe Aruta wrote:
> Hi Eric
>
> - This is the link to GvSIG CE SVN of Sextante:
> https://svn.code.sf.net/p/gvsigce/code/trunk/sextante
>
> - R
Hi Eric
- This is the link to GvSIG CE SVN of Sextante:
https://svn.code.sf.net/p/gvsigce/code/trunk/sextante
- Regarding OJ binding we use. You will find the source code in OpenJUMP
Plugin SVN.
It has been modified during these years in order to a better integration
wof both Software (OpnJUMP a
I also found the sources for the 0.6 version here, directly exported
from code.google.com/p/sextante: https://github.com/danieldupre/sextante
The OpenJUMP bindings are included.
Víctor Olaya could also be contacted to help if needed:
https://github.com/volaya
Finally, I found a version 1.0 of
Thanks.
Is it different from this repository:
- https://joinup.ec.europa.eu/svn/sextante/soft/sextante_lib/
- (OpenJUMP bindings)
https://joinup.ec.europa.eu/svn/sextante/soft/bindings/openjump/
I tried to find the source code of GvSig CE but I failed. Could you
please send us a link to their
>>Less than a day of work should be required (if not less) to update all
the plugins which do not rely on a dependency which relies itself on JTS.
I'm going to test it, to see if it's the case.
Possibly Sextante Will be a problem as we don't have the source code of the
project (it is available on
Here is the list of all the SVN authors (and their number of
contributions) according to the logs:
beckerl 197
bertazza 29
bgudehus 6
clark 6
edso 1305
elnico 54
eric.lemesre 4
infinityedge 2
jammerhund 47
javamap 10
jratike80 22
kdneufeld 2
lreeder 1
ma15569 602
mentaer 465
michaudm 1619
pau
Hi Ede,
Thanks for your welcome and for your answers. See my inline replies for
some of them (I deleted the other parts).
On 09/08/2020 16:40, edgar.sol...@web.de wrote:
hey Eric,
welcome to the team! see my answers below
On 07.08.2020 20:55, Eric wrote:
Then I checked which OJ lib dependen
rs are clearly
> formatted (e.g. with incremented >>), but it is not always the case. Maybe a
> mailingbox configuration problem on my side.
might be, thunderbird is doing a stellar job in this regard ;).. ede
>
> Michaël
>
>> envoyé : 9 août 2020 à 20:46
>> de :
r to me is what exactly will make our code obsolete with new versions of java ? Seems that at the moment, we can write java 8 code and compile it and run it with java 11 or more isn't it ?Michaël >> envoyé : 9 août 2020 à 17:40>> de : edgar.sol...@web.de>> à : jump-pilot-devel@list
me is what exactly will make our code
> obsolete with new versions of java ? Seems that at the moment, we can write
> java 8 code and compile it and run it with java 11 or more isn't it ?
>
> Michaël
>
>
>
>> envoyé : 9 août 2020 à 17:40
>> de : edgar.sol...@web.de
Thanks for your detailed answer Ede,Not sure I get everything about the pom's problem, but I agree with all your proposition concerning OpenJUMP evolution.One point which is not clear to me is what exactly will make our code obsolete with new versions of java ? Seems that at the moment, we can wr
hey Eric,
welcome to the team! see my answers below
On 07.08.2020 20:55, Eric wrote:
> Hi all,
>
> Here are the different steps I made to try updating JTS to at least 1.15, the
> last one being 1.17.
>
>
> The first thing I did was to install OpenJUMP (core / trunk) via SVN in my
> IDE.
>
> I r
30 matches
Mail list logo
