Problem Description: Just like this
I have a local warehouse, build path in the rack package is not missing, pom file does not have any red fork
Resolution process:
At the beginning of the pom file update download less than 4 rack package, I took a lot of online parlance, delete the corresponding rack package location files, let it re-download, invalid.
And then I got a guy to send me. After the package is added to the local by the build path (and the corresponding dependency in the Pom is commented out), re-update,build the path of the rack package is not missing, but the pom file has this problem, cannot read.
Workaround:
When introducing a local rack package, try to avoid adding it directly to build path, and take the local jar via MAVEN.
Create the Libs folder under the project root directory, put in a missing rack package,
In the Pom file, the following configurations are configured for the jars that are not downloaded:
Re-clean,maven update to resolve.