You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/04/18 13:43:14 UTC

[jira] [Resolved] (TAJO-752) Escalate sub modules in tajo-core into the top-level modules

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

Hyunsik Choi resolved TAJO-752.
-------------------------------

    Resolution: Fixed

Thanks all guys. Fixed it as resolved.

> Escalate sub modules in tajo-core into the top-level modules
> ------------------------------------------------------------
>
>                 Key: TAJO-752
>                 URL: https://issues.apache.org/jira/browse/TAJO-752
>             Project: Tajo
>          Issue Type: Task
>          Components: build
>    Affects Versions: 0.8, 0.9
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.8, 0.9
>
>
> We should publish Tajo jar files to public maven. This is the right time to arrange the maven modules. I think that there are rarely working issues which ca cause conflicts to the refactoring. My proposal is to escalate sub modules in tajo-core into the top-level modules as follows:
> * tajo-core/tajo-pullserver -> /tajo-yarn-pullserver
> * tajo-core/tajo-core-backend -> /tajo-core
> I'm looking forward to hearing you guys' ideas.
> Regards,
> Hyunsik



--
This message was sent by Atlassian JIRA
(v6.2#6252)