You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/10/19 15:58:00 UTC

[jira] [Resolved] (IMPALA-10198) Unify Java components into a single maven project

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

Joe McDonnell resolved IMPALA-10198.
------------------------------------
    Fix Version/s: Impala 4.0
         Assignee: Joe McDonnell
       Resolution: Fixed

> Unify Java components into a single maven project
> -------------------------------------------------
>
>                 Key: IMPALA-10198
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10198
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 4.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>             Fix For: Impala 4.0
>
>
> Currently, there are multiple maven projects in Impala's source. Each one is built separately with a separate maven invocation, while sharing a parent pom (impala-parent/pom.xml). This requires artificial CMake dependencies to avoid concurrent maven invocations (e.g. [https://github.com/apache/impala/commit/4c3f701204f92f8753cf65a97fe4804d1f77bc08]). 
> We should unify the Java projects into a single project with submodules. This will allow a single maven invocation. This makes it easier to add new Java submodules, and it fixes the "mvn versions:set" command.



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