Yes, there is going to be a problem: the build will fail because the dependency is missing.
As answered by Chandana from the post you referenced:
you need to download the JAR file and manually install it in to your local repo.
e.g. I suppose that this is the jar in question, download it to some directory, create a file jsr173.pom in the same directory:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<groupId>com.bea.xml</groupId>
<artifactId>jsr173-ri</artifactId>
<version>1.0</version>
</project>
and install it to your local repo like this:
mvn install:install-file -Dfile=jsr173-ri-1.0.jar -DpomFile=jsr173.pom
and the build will pass. The file name and pomFile name will be regenerated by maven according to the data from the jsr173.pom file.
Is this possible?
Yes, it is possible that the JAR file is missing from the repo. It can be because it is a parent pom, but if it is pom referencing a JAR file then that dependency effectively becomes unusable meaning that you have to solve it with the above procedure to use it.
Why?
License issues, it is a copyright reference implementation, see here. It looks like this is a relativley common situation, see this answer.
