On 18.02.2021 19:19, Michaud Michael wrote: > > Hi Ede, jumpers, whoops, busy. forgot to answer your mail about renaming the github branch. ... ok, did that just now.
> It seems that the whole build process can be managed from github with github > actions. > > https://docs.github.com/en/actions <https://docs.github.com/en/actions> > > https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven > > <https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven> > > Do you ever used that ? nope. just know what you read. that it is possible in some way. > As you know how the build was done from Sourceforge repository, you may have > your opinion about how to migrate it to github. > > Let me know if you want to take care of it or if I should try to initiate > something with github tools. whatever you feel like. if you wanna explore github actions go forward. it can't hurt :) just a little busy myself currently > Also, I'm a bit concerned by this page stating that the storage limit for a > free account is 500MB which is already the size of our source repository > > https://docs.github.com/en/github/getting-started-with-github/githubs-products > > <https://docs.github.com/en/github/getting-started-with-github/githubs-products> seems like 'packages storage' is not 'repo storage' https://www.google.com/search?q=github+maximum+repository+size > Also, do you know if a maven repo of OpenJUMP jar file already exists > somewhere. Did you ever do that ? I think that we should mavenize our > extensions, but it will be easier if there is an official repo for > openjump2.0, even if it is a very early 2.0-alpha release. pretty sure the maven build on my server stores one for every build. still i guess it'd be easier to just include the OJ-Core git as a dependency in the extension's maven build. pretty sure that possible somehow. > > Last point (for today) : I'm tempted to abandon the svn history of our > plugins to make the migration process easier. I would be more encline to > clean and uniformize how extensions are managed than to keep all the bits > from the previous repo. What do you think ? my approach would be to cross bridges only when arriving there - meaning: if you are at the point that you want to port an extension to OJ2, put it in a git repo (w or w/o history) work from there. no need for us to import all extensions now bulk i'd say. stay safe, stay sane :).. ede _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
