Re: [JPP-Devel] OpenJUMP and GitHub

[edgar . soldin]

hey Peppe,

the official repo is now
 https://github.com/openjump-gis/openjump

make sure you got 'Eclipse EGit' installed. then you just need to clone the 
above url. enable the branches you are interested in, at least *main* and it 
should work. does for me.

also All,

git workflow's main difference from SVN is mainly he fact that teams/developers 
don't actually work _directly_ on the one branch 'main'. actually they clone 
devel branches for the fix/feature, polish that, squash it and offer it as a 
Pull to the project for review. if all is well that branch's changeset is then 
merged and shows up as single revision in the 'main' branch. a quick web-search 
found this https://opensource.com/article/20/7/git-best-practices where it is 
described quite good. there are probably better howto's out there, but for a 
quic overview it suffices.

to prevent s.o. pushing directly to (actually overwriting) *main* i added some 
protection via 'Branch Protection Rules' 
https://github.com/openjump-gis/openjump/settings/branches . not sure that's 
enough, will have to test it. so please, do not push anything to *main* for the 
time being. let's use Mike's layerable overhaul as a Pull-trial and see how it 
goes :))

..ede

ps. Peppe, something went wrong with your url. check the error. it looks 
concatenated for some reason.

On 14.03.2021 08:14, Giuseppe Aruta wrote:
> Hi all,
> I am trying to connect my eclipse to openjump github repository with no 
> success.
> I tried different "manuals" on web and, for sure, I am newbie for this type 
> of collective programming:  I did something wrong.
> a) following this page
> https://mcuoneclipse.com/2020/10/04/import-projects-from-git-into-eclipse/ 
> 
> I ended to this message:
> immagine.png
>
> b) I see there are two git project 
> https://github.com/openjump-gis/openjump-migration/(Erik) 
>  and 
> https://github.com/openjump-gis/openjump(Michael) 
> , which should I use? Or 
> should I clone the first? Or else?
>
> I will be very grateful for a help
>
> Peppe
>
>
> ___
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>



___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] openjump on github

[edgar . soldin]

On 14.02.2021 12:09, Michaud Michael wrote:
> Hi jumpers,
>
> I just renamed master to main so that all the code now appear in the default 
> branch.

fine by me

> You probably will have to clone again your local repo to have a clean install 
> reflecting the remote repository.

pretty sure that's solvable locally w/p a new checkout. still, find out for 
yourselfs ;)

> We now have to decide if we want to work in a separate dev branch or directly 
> in the main.
>
> Note that working directly in the main does not prevent us to create branches 
> for any change we want to test first or to be reviewed before merging to the 
> main.

afaik working on git is usually done by creating new local branches for 
specific patches. then pushing them to a new personal branch to github or 
gitwhatever and offering a pull from there. that's what i believe it is, while 
the most i ever did was pushing branches for personal use, so i might be wrong 
there.

tl;dr let's read up some how it is supposed to go. and than work accordingly.. 
ede


___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] openjump on github

[Michaud Michael]

Hi jumpers,I just renamed master to main so that all the code now appear in the default branch.You probably will have to clone again your local repo to have a clean install reflecting the remote repository.We now have to decide if we want to work in a separate dev branch or directly in the main.Note that working directly in the main does not prevent us to create branches for any change we want to test first or to be reviewed before merging to the main.Michaël  envoyé : 20 janvier 2021 à 13:07de : edgar.sol...@web.deà : jump-pilot-devel@lists.sourceforge.netobjet : Re: [JPP-Devel] openjump on githubOn 1/20/2021 12:54, Eric wrote:Hi,On 19/01/2021 13:13, edgar.sol...@web.de wrote:>> On 1/19/2021 9:19, Michaud Michael wrote:>>> Hi Jumpers>> Thanks to Eric's guide, I could initialize openjump project on gitub (openjump-gis/openjump) and convert it to jts 1.18.>> It is not perfect (I could not convert 1.5 post_release  tag because of the whitespace in the name :-(), but all in all, I think it is OK.>> tag '1.5 post_release' seems to be there with a %20, or am i missing something?> Please, have a look and let me know if you think so.>> commit history seem to be identical to sf.net svn, though we're missing 2years because of an improper svn mov from /trunk/openjump to /trunk/core . just for completeness sake we should probably transfer this as into a history branch if someone wants to research changes to a specific source file.Would you consider creating a specific repository for these 2 years rather than a branch? It would probably reduce the size of the main repository, which is already quite large (~750MB).See these considerations: https://docs.github.com/en/github/managing-large-files/what-is-my-disk-quota#file-and-repository-size-limitationssounds perfectly reasonable. these 2 missing years are meant as an archive for researching purposes only anyways.As the OJ repository will only come larger over time, it could slow the fetching process.The creation of a specific repository could probably be considered as well to store the former SVN "branches", i.e. oj_stable_1_2 (updated 14 years ago by Stefan Steiniger), 1.2 (updated 14 years ago by Stefan Steiniger), paustin (updated 14 years ago by Paul Austin), 1.3 (updated 12 years ago by Stefan Steiniger), sstein@1863 (updated 11 years ago by Larry Becker) and stable%201.5 (updated 9 years ago by Michael Michaud). All the tags would stay, including the ones in link with the 1.2 and 1.3 versions listed in branches (were these branches some pre-release tests?).currently we dropped those. looking like private devel/test branches to me which can be discarded.>>> I could compile but I still have a problem to run maven.>> I did not migrate plugins at all (not sure how we must proceed yet, some options must be discussed)>> sure, one step after the other. no need to hurry things. generally i'd be in favour of one branch per plugin, but might be swayed otherwise.Ede, do you mean one repository per plugin rather than one branch?indeed. no reason to keep all plugins in one plugin repo.If in the future, the plan is to create/add a plugin manager,there is, since actually always ;)>the option to create a repository per plugin could facilitate their maintenance, especially if the OJ distribution can be used as a Maven dependency for these plugins.totally>>> There are probably plenty of things to improve and fix before we start again to add new code.>> I'll try to list some more precise points to discuss in a future mail.>> ok, looking forward to it. ..edeEricthanks!.. ede___Jump-pilot-devel mailing listJump-pilot-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] openjump on github

[edgar . soldin]

On 1/20/2021 12:54, Eric wrote:
> Hi,
>
> On 19/01/2021 13:13, edgar.sol...@web.de wrote:
>> On 1/19/2021 9:19, Michaud Michael wrote:
>>> Hi Jumpers
>>>
>>> Thanks to Eric's guide, I could initialize openjump project on gitub 
>>> (openjump-gis/openjump) and convert it to jts 1.18.
>>>
>>> It is not perfect (I could not convert 1.5 post_release 
>>> 
>>>  tag because of the whitespace in the name :-(), but all in all, I think it 
>>> is OK.
>> tag '1.5 post_release' seems to be there with a %20, or am i missing 
>> something?
>>
>>> Please, have a look and let me know if you think so.
>> commit history seem to be identical to sf.net svn, though we're missing 
>> 2years because of an improper svn mov from /trunk/openjump to /trunk/core . 
>> just for completeness sake we should probably transfer this as into a 
>> history branch if someone wants to research changes to a specific source 
>> file.
> Would you consider creating a specific repository for these 2 years rather 
> than a branch? It would probably reduce the size of the main repository, 
> which is already quite large (~750MB).
> See these considerations: 
> https://docs.github.com/en/github/managing-large-files/what-is-my-disk-quota#file-and-repository-size-limitations

sounds perfectly reasonable. these 2 missing years are meant as an archive for 
researching purposes only anyways.

> As the OJ repository will only come larger over time, it could slow the 
> fetching process.
>
> The creation of a specific repository could probably be considered as well to 
> store the former SVN "branches", i.e. oj_stable_1_2 (updated 14 years ago by 
> Stefan Steiniger), 1.2 (updated 14 years ago by Stefan Steiniger), paustin 
> (updated 14 years ago by Paul Austin), 1.3 (updated 12 years ago by Stefan 
> Steiniger), sstein@1863 (updated 11 years ago by Larry Becker) and 
> stable%201.5 (updated 9 years ago by Michael Michaud). All the tags would 
> stay, including the ones in link with the 1.2 and 1.3 versions listed in 
> branches (were these branches some pre-release tests?).

currently we dropped those. looking like private devel/test branches to me 
which can be discarded.

>>> I could compile but I still have a problem to run maven.
>>>
>>> I did not migrate plugins at all (not sure how we must proceed yet, some 
>>> options must be discussed)
>> sure, one step after the other. no need to hurry things. generally i'd be in 
>> favour of one branch per plugin, but might be swayed otherwise.
>
> Ede, do you mean one repository per plugin rather than one branch?

indeed. no reason to keep all plugins in one plugin repo.

> If in the future, the plan is to create/add a plugin manager,

there is, since actually always ;)

>the option to create a repository per plugin could facilitate their 
>maintenance, especially if the OJ distribution can be used as a Maven 
>dependency for these plugins.

totally

>>> There are probably plenty of things to improve and fix before we start 
>>> again to add new code.
>>>
>>> I'll try to list some more precise points to discuss in a future mail.
>> ok, looking forward to it. ..ede
>
> Eric

thanks!.. ede


___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] openjump on github

[Eric]

Hi,

On 19/01/2021 13:13, edgar.sol...@web.de wrote:

On 1/19/2021 9:19, Michaud Michael wrote:

Hi Jumpers

Thanks to Eric's guide, I could initialize openjump project on gitub 
(openjump-gis/openjump) and convert it to jts 1.18.

It is not perfect (I could not convert 1.5 post_release 

 tag because of the whitespace in the name :-(), but all in all, I think it is OK.

tag '1.5 post_release' seems to be there with a %20, or am i missing something?


Please, have a look and let me know if you think so.

commit history seem to be identical to sf.net svn, though we're missing 2years 
because of an improper svn mov from /trunk/openjump to /trunk/core . just for 
completeness sake we should probably transfer this as into a history branch if 
someone wants to research changes to a specific source file.
Would you consider creating a specific repository for these 2 years 
rather than a branch? It would probably reduce the size of the main 
repository, which is already quite large (~750MB).
See these considerations: 
https://docs.github.com/en/github/managing-large-files/what-is-my-disk-quota#file-and-repository-size-limitations


As the OJ repository will only come larger over time, it could slow the 
fetching process.


The creation of a specific repository could probably be considered as 
well to store the former SVN "branches", i.e. oj_stable_1_2 (updated 14 
years ago by Stefan Steiniger), 1.2 (updated 14 years ago by Stefan 
Steiniger), paustin (updated 14 years ago by Paul Austin), 1.3 (updated 
12 years ago by Stefan Steiniger), sstein@1863 (updated 11 years ago by 
Larry Becker) and stable%201.5 (updated 9 years ago by Michael Michaud). 
All the tags would stay, including the ones in link with the 1.2 and 1.3 
versions listed in branches (were these branches some pre-release tests?).



I could compile but I still have a problem to run maven.

I did not migrate plugins at all (not sure how we must proceed yet, some 
options must be discussed)

sure, one step after the other. no need to hurry things. generally i'd be in 
favour of one branch per plugin, but might be swayed otherwise.


Ede, do you mean one repository per plugin rather than one branch?

If in the future, the plan is to create/add a plugin manager, the option 
to create a repository per plugin could facilitate their maintenance, 
especially if the OJ distribution can be used as a Maven dependency for 
these plugins.



There are probably plenty of things to improve and fix before we start again to 
add new code.

I'll try to list some more precise points to discuss in a future mail.

ok, looking forward to it. ..ede


Eric



___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] openjump on github

[edgar . soldin]

On 1/19/2021 9:19, Michaud Michael wrote:
> Hi Jumpers
>
> Thanks to Eric's guide, I could initialize openjump project on gitub 
> (openjump-gis/openjump) and convert it to jts 1.18.
>
> It is not perfect (I could not convert 1.5 post_release 
> 
>  tag because of the whitespace in the name :-(), but all in all, I think it 
> is OK.

tag '1.5 post_release' seems to be there with a %20, or am i missing something?

> Please, have a look and let me know if you think so.

commit history seem to be identical to sf.net svn, though we're missing 2years 
because of an improper svn mov from /trunk/openjump to /trunk/core . just for 
completeness sake we should probably transfer this as into a history branch if 
someone wants to research changes to a specific source file.

> I could compile but I still have a problem to run maven.
>
> I did not migrate plugins at all (not sure how we must proceed yet, some 
> options must be discussed)

sure, one step after the other. no need to hurry things. generally i'd be in 
favour of one branch per plugin, but might be swayed otherwise.

> There are probably plenty of things to improve and fix before we start again 
> to add new code.
>
> I'll try to list some more precise points to discuss in a future mail.

ok, looking forward to it. ..ede


___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] openjump on github

[Nicolas Ribot]

The package task runs fine, and by modifying the pom to use jgit as SCM
server, files are created with build number (ie
OpenJUMP-20210119-rcaccfa1928f1bdc1205965d08cf431c50bfb5559-PLUS.zip)

Nicolas

On Tue, 19 Jan 2021 at 11:02, Nicolas Ribot  wrote:

> Hi,
> That's a good news.
>
> I gave it a try, by cloning git repo, then switching to master branch.
> I use IntelliJ IDEA for devs. When running the Maven deploy task, I get
> the error:
> Failed to execute goal
> org.codehaus.mojo:buildnumber-maven-plugin:1.4:create
> (generate-buildnumber) on project OpenJUMP: Cannot get the revision
> information from the scm repository :
> Exception while executing SCM command.
>
> By commenting out the providerImplementations in the
> buildnumber-maven-plugin (pom.xml), the task runs, zip and jar files are
> created (ie: OpenJUMP-20210119-r${version.revision}.jar).
> There is still an error:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
> project OpenJUMP: Deployment failed: repository element was not specified
> in the POM inside distributionManagement element or in
> -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
>
> Nicolas
>
>
> On Tue, 19 Jan 2021 at 09:19, Michaud Michael 
> wrote:
>
>> Hi Jumpers
>>
>> Thanks to Eric's guide, I could initialize openjump project on gitub
>> (openjump-gis/openjump) and convert it to jts 1.18.
>>
>> It is not perfect (I could not convert 1.5 post_release
>> 
>>  tag
>> because of the whitespace in the name :-(), but all in all, I think it is
>> OK.
>>
>> Please, have a look and let me know if you think so.
>>
>> I could compile but I still have a problem to run maven.
>>
>> I did not migrate plugins at all (not sure how we must proceed yet, some
>> options must be discussed)
>>
>> There are probably plenty of things to improve and fix before we start
>> again to add new code.
>>
>> I'll try to list some more precise points to discuss in a future mail.
>>
>> Michaël
>> ___
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] openjump on github

[Nicolas Ribot]

Hi,
That's a good news.

I gave it a try, by cloning git repo, then switching to master branch.
I use IntelliJ IDEA for devs. When running the Maven deploy task, I get the
error:
Failed to execute goal
org.codehaus.mojo:buildnumber-maven-plugin:1.4:create
(generate-buildnumber) on project OpenJUMP: Cannot get the revision
information from the scm repository :
Exception while executing SCM command.

By commenting out the providerImplementations in the
buildnumber-maven-plugin (pom.xml), the task runs, zip and jar files are
created (ie: OpenJUMP-20210119-r${version.revision}.jar).
There is still an error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
project OpenJUMP: Deployment failed: repository element was not specified
in the POM inside distributionManagement element or in
-DaltDeploymentRepository=id::layout::url parameter -> [Help 1]

Nicolas


On Tue, 19 Jan 2021 at 09:19, Michaud Michael 
wrote:

> Hi Jumpers
>
> Thanks to Eric's guide, I could initialize openjump project on gitub
> (openjump-gis/openjump) and convert it to jts 1.18.
>
> It is not perfect (I could not convert 1.5 post_release
> 
>  tag
> because of the whitespace in the name :-(), but all in all, I think it is
> OK.
>
> Please, have a look and let me know if you think so.
>
> I could compile but I still have a problem to run maven.
>
> I did not migrate plugins at all (not sure how we must proceed yet, some
> options must be discussed)
>
> There are probably plenty of things to improve and fix before we start
> again to add new code.
>
> I'll try to list some more precise points to discuss in a future mail.
>
> Michaël
> ___
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

[JPP-Devel] openjump on github

[Michaud Michael]

Hi JumpersThanks to Eric's guide, I could initialize openjump project on gitub (openjump-gis/openjump) and convert it to jts 1.18.It is not perfect (I could not convert 1.5 post_release tag because of the whitespace in the name :-(), but all in all, I think it is OK.Please, have a look and let me know if you think so.I could compile but I still have a problem to run maven.I did not migrate plugins at all (not sure how we must proceed yet, some options must be discussed)There are probably plenty of things to improve and fix before we start again to add new code.I'll try to list some more precise points to discuss in a future mail.Michaël 

___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel