Fail to clone from OpenMBEE Git repository

[open-mbee]

Fail to clone from OpenMBEE Git repository

[landolfa]

One (obvious) solution is to increase the disk quota.

Another one is to change the build system and avoid archiving the jar libraries. This may take quite some time and effort.

By the way, was anybody notified by GitHub about the exceeded quota? I wasn't.

[wobrschalek]

@William1003 please see also the slack conversation
https://openmbee.slack.com/archives/C01FFLQAEUQ/p1666979127664219

[wobrschalek]

we should introduce dependency management and get the jar files from maven central like we do for MMS.
e.g. https://github.com/Open-MBEE/mmsri/blob/develop/build.gradle
is that something you could take on @William1003 ?

[wobrschalek]

for instance, that ST-4.3.1.jar should be pulled from here
https://mvnrepository.com/artifact/org.antlr/ST4/4.3.1
not versioned in the repository

[William1003]

we should introduce dependency management and get the jar files from maven central like we do for MMS. e.g. https://github.com/Open-MBEE/mmsri/blob/develop/build.gradle is that something you could take on @William1003 ?

Thanks a lot! I will try it and I think it would work.

[thomas-bc]

This issue was closed but I still get the error message when cloning the repository. Are there any workarounds?

[landolfa]

Hi @William1003,
any progress in porting COMODO to gradle or maven?

[landolfa]

A temporary workaround is to wait the beginning of the month so that GitHub LFS bandwidth quota is reset to 0 (see https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage).