相信你們開發中老是遇到maven爆紅的狀況,其中的緣由可能有maven倉庫源加載緩慢,能夠在項目中配置本身的私服或者配置國內的景象源,經常使用鏡像源maven的settings文件配置 ``` <mirrors> <mirror> <id>aliyun-central</id> <mirrorOf>central</mirrorOf> <name>aliyun-central</name> <url>http://maven.aliyun.com/nexus/content/repositories/central/</url> </mirror> <mirror> <id>nexus-osc</id> <mirrorOf>osc-central</mirrorOf> <name>Nexus osc</name> <url>http://maven.oschina.net/content/groups/public/</url> </mirror> <mirror> <id>nexus-mvn</id> <mirrorOf>mvn-central</mirrorOf> <name>Nexus mvn</name> <url>http://mvnrepository.com</url> </mirror> <mirror> <id>nexus-spring</id> <mirrorOf>spring-central</mirrorOf> <name>Nexus spring</name> <url>https://repo.spring.io/libs-milestone</url> </mirror>
</mirrors>spring
<profiles> <profile> <id>ali</id> <activation> <jdk>1.8</jdk> </activation> <repositories> <repository> <id>ali</id> <name>Repository for JDK 1.8 builds</name> <url>http://maven.aliyun.com/nexus/content/repositories/central/</url> <layout>default</layout> </repository> </repositories> </profile> <profile> <id>mvn</id> <activation> <jdk>1.8</jdk> </activation> <repositories> <repository> <id>mvn</id> <name>Repository for JDK 1.8 builds</name> <url>http://mvnrepository.com</url> <layout>default</layout> <snapshotPolicy>always</snapshotPolicy> </repository> </repositories> </profile> <profile> <id>spring</id> <activation> <jdk>1.8</jdk> </activation> <repository> <id>spring</id> <name>spring-central</name> <url>https://repo.spring.io/libs-milestone</url> <layout>default</layout> <snapshotPolicy>always</snapshotPolicy> </repository> </profile> </profiles> <activeProfiles> <activeProfile>ali</activeProfile> <activeProfile>spring</activeProfile> <activeProfile>mvn</activeProfile>
</activeProfiles>maven
配置好以後將ide的maven路徑修改 ![](https://s4.51cto.com/images/blog/202010/17/f0d678a24b400f286f6b608b3b783aec.png?x-oss-process=image/watermark,size_16,text_QDUxQ1RP5Y2a5a6i,color_FFFFFF,t_100,g_se,x_10,y_10,shadow_90,type_ZmFuZ3poZW5naGVpdGk=) 刷新maven配置 ![刷新配置](https://s4.51cto.com/images/blog/202010/17/2066bfc32af97c0d6540bea7018c3d21.png?x-oss-process=image/watermark,size_16,text_QDUxQ1RP5Y2a5a6i,color_FFFFFF,t_100,g_se,x_10,y_10,shadow_90,type_ZmFuZ3poZW5naGVpdGk=) 上述操做以後仍是爆紅,實際上maven倉庫裏面有了對應的jar包了,此時只能命令行執行mvn clean compile 或者mvn clean install 看控制檯錯誤,檢查報錯的jar包是否是本身公司的內部jar包,若是是,找到對應jar包的版本路徑和實際maven的路徑 版本是否一一對應 ![](https://s4.51cto.com/images/blog/202010/17/f30392ba94bc7503ee5d7e1fcdb3fc2c.png?x-oss-process=image/watermark,size_16,text_QDUxQ1RP5Y2a5a6i,color_FFFFFF,t_100,g_se,x_10,y_10,shadow_90,type_ZmFuZ3poZW5naGVpdGk=) 上圖中的common 1.0在我本地不存在,最後找到pom文件檢查,發現如今的版本是1.0-SNAPSHOT,改完版本從新執行maven clean installl就能夠了。爲何別人的能夠,是由於別人在改版本以前已經編譯過了,有了對應的jar包在本地倉庫了因此別人的正常你的不正常,加載緩慢重啓ide從新更新便可。