Dependency with different type hides jar dependency from same artifact

Hi all,

I use a setup in which there are Maven modules that create multiple artifacts (using types). Typically this is a jar file (using bnd-maven-plugin) and a tar.gz using a custom assembly.

Using those artifacts (as dependency) is easy, a default dependency for the bundle, and a dependency with explicit type for the tar.gz. From a Maven pov this all works as expected.
However, recently I noticed that the export plugin does not find the jar dependency if it is declared (in the POM) below the tar.gz dependency.
This results in a resolve error where the requirement cannot be found.

Moving the jar above the tar.gz dependency solves this.

Is this a known issue?