#337 add mac architectures

[jan-vcapgemini]

Fixes: #337

Implements:

• os-maven-plugin
• automatic detection of OS and architectures

[coveralls]

Pull Request Test Coverage Report for Build 9840802466

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 61.755%

---

Totals
Change from base Build 9813808982:	0.0%
Covered Lines:	5276
Relevant Lines:	8226

---

💛 - Coveralls

[hohwille]

@jan-vcapgemini thanks for this PR. If I understood this approach correctly, there are issues that Java/Maven reports the architecture not properly normalized (for system property os.arch) so the same thing can get different values depending on the platform.
Therefore insted of profiles triggered by OS activation setting things like this:

       <os.detected.classifier>windows</os.detected.classifier>
       <os.detected.arch>x64</os.detected.arch>

You now use os-maven-plugin to generate such properties in a normalized way. While this seems like a smart and valid approach, you need to be aware that the previous properties where somehow made up by some developer in our team. Even though os-maven-plugin uses the same property names, it does use them not with the same semantics.
IMHO you need to change at least

<releaseName>${project.artifactId}-${os.detected.classifier}-${os.detected.arch}</releaseName>

to

<releaseName>${project.artifactId}-${os.detected.classifier}</releaseName>

or to

<releaseName>${project.artifactId}-${os.detected.name}-${os.detected.arch}</releaseName>

if I read the documentation of that plugin correctly.

Further, we have standardized our architectures differently and use x64 instead of x86_64 so we still might need to find a way how to remap these but this is some nice to have that can also be addressed after merging this PR.

[jan-vcapgemini]

Can be closed because #471 was already merged.