|
|
1. Why is there a snapshot?
Before there were snapshots:
Project A relies on project B. B gives a new version number every time it changes, and then tells A that I've changed the version, and every time I change it, I have to tell it, and sometimes it's a problem if I forget.
It can be seen that no snapshot will bring "wasted version number", communication into a large increase in the problem.
With snapshots:
Project A depends on project B. Every time B changes, it will put a timestamp on it. When A compiles, it will check the timestamp of B. If the timestamp is later than the timestamp of B in the local repository, then it will be updated, otherwise, it will not be updated.
It can be seen that snapshots save the cost of communication, version number costs.
2, snapshot update strategy
Note that snapshots are not updated every time you install them, it depends on the update strategy; snapshot update strategy, there are daily update, always check for updates, never check for updates and customize the time interval update, the default is daily update which means that it is updated once a day, if you want to update it all the time, you can configure it in settings.xml. For example:
(always, daily (default, daily), interval: X (where X is the interval in minutes), or never))
You can also force updates with the command, mvn clean install -U
|
Previous: Spring Cloud Filter through the ContentCachingRequestWrapper get request contentNext: NET/C# features of the CallerMemberName, CallerFilePath, CallerLineNumber
|
发表于 2021-8-10 13:59:31
Relay
