Just into the company, from SVN to get the code down after the introduction of eclipse, usually maven project, often the project will have a red Fork. If you exclude the problem with the code itself, it is generally not a jar package.
Mouse Point open Pom.xml file, in the constraints there is generally red fork, mouse on the general will prompt missing artifact fakepath:dubbo:jar:2.8.5, indicating that the local warehouse is missing jar Package.
If the local repository does not, generally click Maven-update project, he will automatically download.
If your local repository is already there, it is often not previously Complete. Lastupdated's jar package was not deleted. Then you can delete it directly. Then click on the project run As-maven install or clean install to compile the installation again, and then Maven-update project to update the next item, the Red Cross will Disappear.
Sometimes the red fork and you find that the import COM will appear in the Code. XXXXXX cannot be resolved, This is your choice project-->clean, the problem is Solved. If not, you can try to delete the import, click ctrl+shift+o, re-import.
"Java" svn download maven project to eclipse, Project Red fork, pom.xml appears missing artifact fakepath:dubbo:jar:2.8.5, etc. missing jar package condition