it should definitely go up the chain. If you see it in mvn help:effective-pom, Resolver should see it as well. You can also try to debug what resolver actually see by grabbing MavenWorkingSession here:
It should work with 2.1.1, there were some fixes w.r.t. classifiers and types in 2.2.0 stream. If that does not work with 2.2.0-beta-1, it's most likely a bug.
Sadly, it does not work for me with both 2.1.1 and 2.2.0-beta-1.
I'm getting :
org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to get version for dependency specified by org.assert:assertj-core:compile, it was not provided in neither <dependencyManagement> nor <dependencies> sections.
And in the effective pom I see:
I thought that would be implicit. Should I specify scope too?
I will try to isolate this problem and share it through GitHub.
Is that assertj-core directly in <dependency> or <dependencyManagement> of parent? Or is it transitive dependency? The closest test case in integration test for the former is here - which seems pretty much like your test case: