If the project is building with maven you cannot deploy an artifact with missing dependencies because maven will try to resolve deps and build the project first. If you are using mvn deploy:deploy-file and just deploying the jar and pom manually, then the dependencies are not resolved first.
But the artifacts are probably resolvable from a local repo.
The scenario in the other thread clearly shows the problem.
Ok, I see the problem. Yes, there should be a way to check that dependencies are available remotely when deploying.