use reactor artifacts before dependency or plugin artifacts

[zuckel]

Currently if an artifact is both a project artifact (a sibling module) and also a dependency artifact, the latter one will win and make it to the classpath. An artifact from the repository will then be used instead of the current one from the active build.
This will break the build if there were any changes to one module that need to be visible to another module.

The solution is to reorder dependencies when building the class-path such that reactor artifacts are always considered first.

The scenario can happen e.g. in presence of a BOM such as created by cyclonedx-maven-plugin.

[bmarwell]

Hi @zuckel!
Thanks a lot for your PR! I think we can include it in the next release.

I think we should create an issue for this and tag the commit message accordingly (e.g. [#xx] use reactor artifacts before dependency or plugin artifacts).
Thanks for the test case as well!

[zuckel]

Ok, I'll open in issue and change the commit message.