You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Norbert Kalmar (JIRA)" <ji...@apache.org> on 2018/10/22 20:07:00 UTC

[jira] [Updated] (ZOOKEEPER-3029) Create pom.xml for jute and server

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

Norbert Kalmar updated ZOOKEEPER-3029:
--------------------------------------
    Summary: Create pom.xml for jute and server  (was: Create pom.xml for jute, server, client and common)

> Create pom.xml for jute and server
> ----------------------------------
>
>                 Key: ZOOKEEPER-3029
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3029
>             Project: ZooKeeper
>          Issue Type: Sub-task
>          Components: build, scripts
>    Affects Versions: 3.6.0
>            Reporter: Norbert Kalmar
>            Assignee: Norbert Kalmar
>            Priority: Major
>
> After the directory structures has been created, it is time to create the pom files for all the modules, and create the build hierarchy. 
> At first, ant should remain in place until we are sure maven works fine.
> jute, server, client and common should be priority first. docs is handled in a different jira, as it is also being migrated. Recipes and contrib will remain for last.
> The different modules will get their maven structure:
> {noformat}
> zookeeper-[something]
> | -src
> |    | -main
> |    |    | -java
> |    |    |     \org...
> |    |    \resources
> |    | -test (unit tests only)
> |    |    | -java
> |    |    |   \org...
> |    |    \ resources
> |    | - it (integration tests)
> |    \pom.xml
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)