Transient dependencies of type pom not in war

[jurgweilenmannbradyplc]

If you a module (added to jarResource) has a dependency of type pom, the war does not include these dependencies.

Example: the module listed as jarResource has a dependency to

                <dependency>
                    <groupId>org.jboss.as</groupId>
                    <artifactId>jboss-as-ejb-client-bom</artifactId>
                    <type>pom</type>
                    <scope>compile</scope>
                </dependency>

In that case, dependencies listed in jboss-as-ejb-client-bom are not included in the war.

They were included in version 1.0-beta-4, but not in 1.0-beta-6 nor 1.0-beta-7-SNAPSHOT

[RangerRick]

I can confirm this is regressed in 1.0-beta-7. I was previously using a version of 1.0-beta-7-SNAPSHOT that was built on April 24th, 2014 that did follow type=pom dependencies but I don't have a *-sources.jar so I'm not sure if we modified our build to revert a previous change, or if it's the same as the beta-7 upstream.