Maven cannot determine the solution based on actual time.

Reprinted from http://my.oschina.net/xyly624/blog/122743

Today, when I created a jar package, I found that the configuration of a new jar package was added to the POM file.
The first countermeasure is the merge format. However, the format of the project description is correct. You have to configure the configuration directly from the maven central repository.
The second countermeasure is the loss of dependency in Maven. Check that only the POM file exists and the jar package does not exist. If the Hacker sets up a ladder and updates it again, the jar package is not updated. If a file named "lastupdated" already exists in the image, it indicates an update error. However, this type of file does not exist in the image! Strange. I opened my impression and found the transcript I previously recorded. After I wrote it, I succeeded.The jar package cannot be downloaded due to dependency failure.. I would like to share this with you.

Bash example (It should be based on the website):

# Remove all missing find ~ /. M2-name "*. lastupdated"-exec grep-Q "cocould not transfer" {}\;-print-exec RM {}\;

The above is available in Ubuntu 12.04.