[ 
https://issues.apache.org/jira/browse/ARROW-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liya Fan resolved ARROW-10333.
------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Issue resolved by pull request 8483
[https://github.com/apache/arrow/pull/8483]

> [Java] Remove split packages in arrow-memory-core and arrow-vectors
> -------------------------------------------------------------------
>
>                 Key: ARROW-10333
>                 URL: https://issues.apache.org/jira/browse/ARROW-10333
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: 1.0.1
>            Reporter: Benjamin Wilhelm
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> TheĀ  java package (org.apache.arrow.util) is provided in two different 
> artifacts
>  * arrow-memory-core: ([Link to 
> GitHub|https://github.com/apache/arrow/tree/master/java/memory/memory-core/src/main/java/org/apache/arrow/util])
>  * arrow-vectors: ([Link to 
> GitHub|https://github.com/apache/arrow/tree/master/java/vector/src/main/java/org/apache/arrow/util])
> This is causing trouble when using OSGI dependency management. After 
> converting the maven artifacts to OSGI bundles the package is available via 
> two chains (which is not allowed).
> Additionally, the Java 9+ module system (JPMS) does not allow for split 
> packages either. See 
> [here|https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html].
> This was mentioned in the [mailing 
> list|https://lists.apache.org/thread.html/r750c627757a7d6739651a73bd51c36fc9ade7c819eb509ed99fd03c0%40%3Cuser.arrow.apache.org%3E].
> Possible solutions are:
> * Renaming the packages to {{org.apache.arrow.vector.util}} and 
> {{org.apache.arrow.memory.util}}
> * Moving the classes from vector to memory-core



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to