|
Hi Ede, jumpers, 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/guides/building-and-testing-java-with-maven Do you ever used that ? 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. 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 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. 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 ? Michaël |
_______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
