On Mon, Jul 11, 2016 at 11:08 AM, Marcelo Vanzin <van...@cloudera.com> wrote:
> On Mon, Jul 11, 2016 at 2:34 AM, sebb <seb...@gmail.com> wrote: > > However bundling multiple native binaries is going to make it tricky to > release. > > How will it be done? The native parts will have to be built separately > > and then combined somehow. > > The way I'd do it is to have separate artifacts for each native > library, and then a final job that merges all those into a final > "commons-crypto-all" artifact containing all the native libraries. > That would mean a single artifact ultimately deployed as part of a > commons-crypto release, but I don't know how easy it is to pull that > off as far as build infrastructure goes. > > Another option is to actually deploy each native artifact separately, > and have the "all" artifact be just a dummy artifact that depends on > all the others; so no jar merging or anything. That might be easier. > Maybe. > It does not need to be a dummy as much as a BOM. We do this in Log4j 2. Gary > > -- > Marcelo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
