You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:09:03 UTC
[jira] [Commented] (ARROW-397) [Java] Include compiled Flatbuffers sources in release artifacts
[ https://issues.apache.org/jira/browse/ARROW-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17657431#comment-17657431 ]
Rok Mihevc commented on ARROW-397:
----------------------------------
This issue has been migrated to [issue #16025|https://github.com/apache/arrow/issues/16025] on GitHub. Please see the [migration documentation|https://github.com/apache/arrow/issues/14542] for further details.
> [Java] Include compiled Flatbuffers sources in release artifacts
> ----------------------------------------------------------------
>
> Key: ARROW-397
> URL: https://issues.apache.org/jira/browse/ARROW-397
> Project: Apache Arrow
> Issue Type: Bug
> Components: Java
> Reporter: Wes McKinney
> Priority: Major
>
> 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?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)