The bom is to be imported in dependencyManagement, to define the versions for the real dependencies, needed by the standalone application.
AFAIK these boms can either be used as an dependencyManagement import, or as a straight dependency, as you have it. (I am using it as a straight dependency too, to bring in all of the JARs in the bom's dependencies).
It looks like the problem might be just a missing <type>. Try this:
Many JBoss libraries aren't in Maven central. Instead, they are in a JBoss maven repository.
You can search for libraries here: https://repository.jboss.org/nexus/#welcome
Once you find what you're looking for, you can click the "Artifact" tab and see that it is in JBoss Releases. The URL I have for that is https://repository.jboss.org/nexus/content/repositories/releases/
Guide for working with multiple maven repositories: Maven – Guide to using Multiple Repositories
well this is not the case here.
whole groupId "org.wildfly" is synced to maven central.
for example wildfly-client-bom Maven Repository: org.wildfly » wildfly-ejb-client-bom
problem is as Eduardo & Darren pointed out, dependency spec if wrongly configured.