Also see the xolstice protobuf-maven-plugin which marries up nicely with
the OS properties.
On 5/30/18 3:40 PM, Brian Loss wrote:
If I understand what you are asking correctly, os-maven-plugin [1] is what you
are looking for. It will determine the os name and arch (it puts them in
properties os.detected.name and os.detected.arch) and you can use those values
to declare the right executableDependency [2] for the exec-maven-plugin.
[1]
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22kr.motd.maven%22%20AND%20a%3A%22os-maven-plugin%22
[2]
https://www.mojohaus.org/exec-maven-plugin/examples/example-exec-using-executabledependency.html
________________________________________
From: Christopher [ctubb...@apache.org]
Sent: Wednesday, May 30, 2018 3:17 PM
To: dev@accumulo.apache.org
Subject: Re: Java (eventually) dropping Serialization
I wasn't aware they were publishing pre-built binaries for various
platforms to Maven Central. That could be quite useful if we could
automatically download the correct one during the Maven build, and use that
to generate the code. It could still be problematic if they are dynamically
linked to specific version ranges of system libraries, but I'd be
interested in trying. Do you know if that tooling already exists as a Maven
plugin or similar?
