If you are using a public server instead of a private server, you should consider whether the package that a certain jar A depends on exists on the public server. If it is a private server, upload a copy if it does not exist
Looking at the poster’s problem, it seems that the local project depends on the local project.
Check if there are any errors in the pom.xml of project A. As long as there is an error, other dependencies will be red.
Usually eclipse has prompts.
If you are using a public server instead of a private server, you should consider whether the package that a certain jar A depends on exists on the public server. If it is a private server, upload a copy if it does not exist
mvn dependency:tree -Dverbose
to look at the dependency treeLooking at the poster’s problem, it seems that the local project depends on the local project.
Check if there are any errors in the pom.xml of project A. As long as there is an error, other dependencies will be red.
Usually eclipse has prompts.
That’s because the transitivity of other dependencies in the jar A you depend on is not set up properly