Maven dependencies targeting a type different from the default one are not supported

In some (fortunately very rare so far) cases, you can have a Maven dependency request an artifact which is not the default one (with a different type or classifier for example) and this cause collisions problems if several artifacts associated with the same artifact id are downloaded.

We would need to introduce a way to have several extensions in such a case (most probably by including the classifier and the alternate type in the extension id). It's already partially supported by resolve (but disabled right now) but not by the dependency handling side.