Problem Description:
Since there is this jar package, why is it still reporting an error?
Inadvertently check the dependencies through the dependency:tree command and find:
This shows that the core-common.jar package depends on paas-thirdparty-bom-1.3.5.pom. By checking the local repository, it is found that this file also exists, which is a strange problem.
After extensive comparison, it was found that:
The problem is in _remote.repositories
>nexus indicates that this dependency is downloaded from the private server. At this time, I can't connect to the private server (these dependencies are copied to me by others).
View a dependency that can be displayed normally and find _remote.repositories
This is downloaded from the remote repository.
So I have an idea: find the corresponding _remote.repositories and change nexus= to central=
In the end it turned out to be a success.
Note: When the above problem reports an error, although the current core-common dependency exists, its transitive dependency cannot be loaded. The reason is caused by nexus= of _remote.repositories.
After all the dependent _remote.repositories are changed, the project will not report an error, and its transitive dependencies will be loaded in
Reprinted in: https://my.oschina.net/yibuliushen/blog/1550292