Document that os-maven-plugin is needed to resolve dependencies

[shadjiiski]

The main pom.xml of microbean-helm depends on
io.netty:netty-tcnative-boringssl-static:jar:${os.detected.classifier}
where the os.detected.classifier property is computed by the os-maven-plugin.
This commit updates the README.md to reflect the need of the
os-maven-plugin.

[shadjiiski]

This is just a little something that helped me with this error

Failure to find io.netty:netty-tcnative-boringssl-static:jar:${os.detected.classifier}:2.0.6.Final in https://oss.sonatype.org/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of maven-central has elapsed or updates are forced -> [Help 1]

cheers!

[jiaj12]

this solution not work for me, i did import the jars manually instead

[shadjiiski]

@jiaj12, what was the behavior of the mvn install command after you added the os-maven-plugin to the list of build extensions in your pom file? In my case, the plugin specific properties are computed and printed before the module build order is determined. I get something like this in the log:

[INFO] ------------------------------------------------------------------------
[INFO] Detecting the operating system and CPU architecture
[INFO] ------------------------------------------------------------------------
[INFO] os.detected.name: linux
[INFO] os.detected.arch: x86_64
...
[INFO] os.detected.classifier: linux-x86_64
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] module-1
[INFO] module-2
...

Adding the build extension should fix your build, however, you might still be getting error messages in your IDE, especially if you are using Eclipse. As stated in the readme of the os-maven-plugin you will have to add the os-maven-plugin as an Eclipse plugin to deal with that. I found that you will also need to use the right version of the plugin as well (1.5.0.Final in the microbean-helm case). Is this what you meant when you said that you had to import the jars instead of modifying the pom.xml?