Also called a "A-BOM" in EAP, or "depchain" in AS, this POM aggregates dependencies for a project, in the right scope, in one view:

For instance:

foo-api
foo-impl

foo
  dep:
    foo-api (compile)
    foo-impl (runtime)

In this case, "foo" would be the module we're looking to create. A user then makes a dependency upon this POM in coordination with a dep on the BOM in "import" scope in depMgt (in order to honor exclusions).

An example of this in use is:

https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L128
https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L156

In the example above we have the dep on the AS7 API in two places as required; in turn the AS7 API POM exports out transitives as we need. In that case the AS7 API is both BOM and Library POM.