This repo is too big due to having the maven local cache files

[LinuxSuRen]

[JohnNiang]

I want to try to resolve this issue.

[LinuxSuRen]

Cool! Please don't forget to describe your solutions before you get it started.

[JohnNiang]

Alright.

[JohnNiang]

I'm trying to use this approach to remove artifacts folder.

[JohnNiang]

#78 Resolve this issue, but may can not be merged into master branch directly.

[LinuxSuRen]

So we can reduce the size of this repo by pushing the changes directly to the master branch. Right?

But there's another thing we need to consider. What do they need to do after we removing the maven local cache files? Please consider providing a solution for people who might also want to use the cache files.

[JohnNiang]

What kind of scene needs to add offline mode in demo projects, is it reasonable in itself? This may make us more concerned.

[JohnNiang]

If offline mode is very necessary for someone, we can provide an offline packaging method for him/her.

[LinuxSuRen]

For some users, their environment has no access to the internet. It's very helpful to offer them a solution. The most important thing is that remove the maven files without a solution will be a break change for the users.

[JohnNiang]

We can guide user to execute the following command:

mvn -gs configuration/settings.xml clean verify
mvn -gs configuration/settings.xml package -DskipTests

The two commands above will result artifacts folder for offline mode use.

And then they can push the artifacts folder into their repo(public or private, online or offline).

[LinuxSuRen]

This is absolutely a good way to collect the cache files. How about we just do this directly? I mean we can run the command in the GitHub actions, then put those files into an image, push the image to the docker hub. So users can reuse it instead of building it every time.