On 1/5/18 9:55 AM, Keith Turner wrote:
Obviously, there are many ways to go about this. If there is buy-in from
other folks, adding some new assembly descriptors and making it a part of
the Maven build (perhaps, optionally generated) would be the easiest in
terms of maintenance. However, I don't want to push for that if it's just
going to be ignored by folks. I'll be creating something to support this one
way or another.
Do you have anything to share? I would be interested in reviewing this.
Nothing yet. My plan is to take the stock bin-tarball, split the files
up into two lists to make sure I have the separation correct (that
things actually work). Then, I can implement it however we want.
Any thoughts/opinions? Would this have any value to other folks?
This is slightly unrelated, but it would be nice to lower the number
of dependencies for the client side code and possibly shade in
libthrift.
Yup. Agreed.
