Recently the company's project is ready to use MAVEN, switching down is very simple, but the compilation found a very strange phenomenon, is not configured in the Pom jar package or the version of the jar is not configured to appear in the Lib folder, at first thought it was exclusions not set, But after repeated experiments found that can not completely solve the problem, some belong to the project team customized jar package also has multiple versions, and some computers are compiled without problems, and then think of whether the local MAVEN warehouse is broken, delete re-download, or not, Then I accidentally saw a post saying that the same folder under the name of the project causes Maven to refer to the project as a priority (my project uses git management to download multiple branches of the project under the Git folder), although not the same as the problem I encountered, But also try to switch the MAVEN branch into another separate folder, did not expect to solve, inexplicably duplicate jar package did not, but now only know how to solve this problem but do not know why this, With the Eclipse Maven plugin embedded3.0.2, is it a maven version bug?
A large number of duplicate jar packages are present in the Java Project switch maven compilation
