apache / apache/arrow-java

[Java] Include compiled Flatbuffers sources in release artifacts

未關閉
#293 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
Type: bug
主要語言
Java
星號
94
分支
152
平均合併
3 天 16 小時
30 天內合併 PR
11

描述

I'm seeing the flatc that's available in Maven foul up users because it depends on a version of glibc (2.14) which is too new for many enterprise Linux users. It would be better for the Arrow Java artifacts to not depend on flatc at all, if possible.

We could check the compiled sources into source control, but that seems less than ideal. Is there a clean way bundle them at packaging time?

**Reporter**: [Wes McKinney](https://issues.apache.org/jira/browse/ARROW-397) / @wesm

**Note**: *This issue was originally created as [ARROW-397](https://issues.apache.org/jira/browse/ARROW-397). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*

貢獻指南

開啟貢獻指南

研究方向

先檢視 issue 中連結的 migration 文件,以及 Arrow Java artifacts 的 Maven packaging 設定。確認目前 flatc 的使用方式,並定義一條在 packaging 時納入已編譯 FlatBuffers sources 的路徑,而不需要在使用時具備 flatc;完成的標準是,release artifacts 不再針對這些 sources 依賴該 binary。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
java
領域
build-system, release
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
基本清楚
新手友好度
30/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。