[jira] [Updated] (ZOOKEEPER-3032) Step 1.6 - Create zk-server maven structure
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norbert Kalmar updated ZOOKEEPER-3032:
--
Description:
Create a project structure that separates the different parts of ZooKeeper into
a more meaningful packages for the future maven build.
This should be done in iterations to limit the impact.
* First iteration - safe changes including moving src/docs to zk-docs, creating
zk-it empty directory. Build and conf directory remains unchanged. These
changes also have minimum impact on PR’s.
* Second iteration - move src/recipes to zk-recipes.
* Third iteration - move src/contrib to zk-contrib.
* Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
* Fifth iteration - move jute under src directory
* *Sixth iteration* - move src/java/main to zk-server, also separate client
code from server code, move common files to zookeeper-common.
*
*Modification*
It is not feasible to separate core java files into server, client and common.
It will remain in zookeeper-server.
{noformat}
zookeeper
| -bin
| -conf
| -jute
| -zookeeper-client
|| -zookeeper-client-c
|| - *REMOVED* zookeeper-client-java
| - *REMOVED* zookeeper-common
| -zookeeper-contrib
|| -zookeeper-contrib-fatjar
|| -zookeeper-contrib-huebrowser
|| -zookeeper-contrib-loggraph
|| -zookeeper-contrib-monitoring
|| -zookeeper-contrib-rest
|| -zookeeper-contrib-zkfuse
|| -zookeeper-contrib-zkperl
|| -zookeeper-contrib-zkpython
|| -zookeeper-contrib-zktreeutil
|\ -zookeeper-contrib-zooinspector
| -zookeeper-docs
| -zookeeper-it (integration tests)
| -zookeeper-server
| -zookeeper-recipes
|| -zookeeper-recipes-election
|| -zookeeper-recipes-lock
\\ -zookeeper-recipes-queue
{noformat}
was:
Create a project structure that separates the different parts of ZooKeeper into
a more meaningful packages for the future maven build.
This should be done in iterations to limit the impact.
* First iteration - safe changes including moving src/docs to zk-docs, creating
zk-it empty directory. Build and conf directory remains unchanged. These
changes also have minimum impact on PR’s.
* Second iteration - move src/recipes to zk-recipes.
* Third iteration - move src/contrib to zk-contrib.
* Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
* Fifth iteration - move jute under src directory
* *Sixth iteration* - move src/java/main to zk-server, also separate client
code from server code, move common files to zookeeper-common.
{noformat}
zookeeper
| -bin
| -conf
| -jute
| -zookeeper-client
|| -zookeeper-client-c
|| -zookeeper-client-java
| -zookeeper-common
| -zookeeper-contrib
|| -zookeeper-contrib-fatjar
|| -zookeeper-contrib-huebrowser
|| -zookeeper-contrib-loggraph
|| -zookeeper-contrib-monitoring
|| -zookeeper-contrib-rest
|| -zookeeper-contrib-zkfuse
|| -zookeeper-contrib-zkperl
|| -zookeeper-contrib-zkpython
|| -zookeeper-contrib-zktreeutil
|\ -zookeeper-contrib-zooinspector
| -zookeeper-docs
| -zookeeper-it (integration tests)
| -zookeeper-server
| -zookeeper-recipes
|| -zookeeper-recipes-election
|| -zookeeper-recipes-lock
\\ -zookeeper-recipes-queue
{noformat}
> Step 1.6 - Create zk-server maven structure
> ---
>
> Key: ZOOKEEPER-3032
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3032
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: build, scripts
>Affects Versions: 3.6.0
>Reporter: Norbert Kalmar
>Assignee: Norbert Kalmar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0, 3.5.5, 3.4.14
>
> Time Spent: 12h 40m
> Remaining Estimate: 0h
>
> Create a project structure that separates the different parts of ZooKeeper
> into a more meaningful packages for the future maven build.
> This should be done in iterations to limit the impact.
> * First iteration - safe changes including moving src/docs to zk-docs,
> creating zk-it empty directory. Build and conf directory remains unchanged.
> These changes also have minimum impact on PR’s.
> * Second iteration - move src/recipes to zk-recipes.
> * Third iteration - move src/contrib to zk-contrib.
> * Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
> * Fifth iteration - move jute under src directory
> * *Sixth iteration* - move src/java/main to zk-server, also separate client
> code from server code, move common files to zookeeper-common.
> *
> *Modification*
> It is not feasible to separate core java files into server, client and
> common. It will remain in zookeeper-server.
> {noformat}
> zookeeper
> | -bin
> | -conf
> | -jute
> | -zookeeper-client
> || -zookeeper-client-c
> || -
[jira] [Updated] (ZOOKEEPER-3032) Step 1.6 - Create zk-server maven structure
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ZOOKEEPER-3032:
--
Labels: pull-request-available (was: )
> Step 1.6 - Create zk-server maven structure
> ---
>
> Key: ZOOKEEPER-3032
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3032
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: build, scripts
>Affects Versions: 3.6.0
>Reporter: Norbert Kalmar
>Assignee: Norbert Kalmar
>Priority: Major
> Labels: pull-request-available
>
> Create a project structure that separates the different parts of ZooKeeper
> into a more meaningful packages for the future maven build.
> This should be done in iterations to limit the impact.
> * First iteration - safe changes including moving src/docs to zk-docs,
> creating zk-it empty directory. Build and conf directory remains unchanged.
> These changes also have minimum impact on PR’s.
> * Second iteration - move src/recipes to zk-recipes.
> * Third iteration - move src/contrib to zk-contrib.
> * Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
> * Fifth iteration - move jute under src directory
> * *Sixth iteration* - move src/java/main to zk-server, also separate client
> code from server code, move common files to zookeeper-common.
> {noformat}
> zookeeper
> | -bin
> | -conf
> | -jute
> | -zookeeper-client
> || -zookeeper-client-c
> || -zookeeper-client-java
> | -zookeeper-common
> | -zookeeper-contrib
> || -zookeeper-contrib-fatjar
> || -zookeeper-contrib-huebrowser
> || -zookeeper-contrib-loggraph
> || -zookeeper-contrib-monitoring
> || -zookeeper-contrib-rest
> || -zookeeper-contrib-zkfuse
> || -zookeeper-contrib-zkperl
> || -zookeeper-contrib-zkpython
> || -zookeeper-contrib-zktreeutil
> |\ -zookeeper-contrib-zooinspector
> | -zookeeper-docs
> | -zookeeper-it (integration tests)
> | -zookeeper-server
> | -zookeeper-recipes
> || -zookeeper-recipes-election
> || -zookeeper-recipes-lock
> \\ -zookeeper-recipes-queue
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-3032) Step 1.6 - Create zk-server maven structure
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norbert Kalmar updated ZOOKEEPER-3032:
--
Description:
Create a project structure that separates the different parts of ZooKeeper into
a more meaningful packages for the future maven build.
This should be done in iterations to limit the impact.
* First iteration - safe changes including moving src/docs to zk-docs, creating
zk-it empty directory. Build and conf directory remains unchanged. These
changes also have minimum impact on PR’s.
* Second iteration - move src/recipes to zk-recipes.
* Third iteration - move src/contrib to zk-contrib.
* Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
* Fifth iteration - move jute under src directory
* *Sixth iteration* - move src/java/main to zk-server, also separate client
code from server code, move common files to zookeeper-common.
{noformat}
zookeeper
| -bin
| -conf
| -jute
| -zookeeper-client
|| -zookeeper-client-c
|| -zookeeper-client-java
| -zookeeper-common
| -zookeeper-contrib
|| -zookeeper-contrib-fatjar
|| -zookeeper-contrib-huebrowser
|| -zookeeper-contrib-loggraph
|| -zookeeper-contrib-monitoring
|| -zookeeper-contrib-rest
|| -zookeeper-contrib-zkfuse
|| -zookeeper-contrib-zkperl
|| -zookeeper-contrib-zkpython
|| -zookeeper-contrib-zktreeutil
|\ -zookeeper-contrib-zooinspector
| -zookeeper-docs
| -zookeeper-it (integration tests)
| -zookeeper-server
| -zookeeper-recipes
|| -zookeeper-recipes-election
|| -zookeeper-recipes-lock
\\ -zookeeper-recipes-queue
{noformat}
was:
Create a project structure that separates the different parts of ZooKeeper into
a more meaningful packages for the future maven build.
This should be done in iterations to limit the impact.
* First iteration - safe changes including moving src/docs to zk-docs, creating
zk-it empty directory. Build and conf directory remains unchanged. These
changes also have minimum impact on PR’s.
* Second iteration - move src/recipes to zk-recipes.
* Third iteration - move src/contrib to zk-contrib.
* Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
* Fifth iteration - move jute under src directory
* *Sixth iteration* - move src/java/main to zk-server, which will be further
separated in Step 2.
{noformat}
zookeeper
| -bin
| -conf
| -jute
| -zookeeper-client
|| -zookeeper-client-c
|| -zookeeper-client-java
| -zookeeper-common
| -zookeeper-contrib
|| -zookeeper-contrib-fatjar
|| -zookeeper-contrib-huebrowser
|| -zookeeper-contrib-loggraph
|| -zookeeper-contrib-monitoring
|| -zookeeper-contrib-rest
|| -zookeeper-contrib-zkfuse
|| -zookeeper-contrib-zkperl
|| -zookeeper-contrib-zkpython
|| -zookeeper-contrib-zktreeutil
|\ -zookeeper-contrib-zooinspector
| -zookeeper-docs
| -zookeeper-it (integration tests)
| -zookeeper-server
| -zookeeper-recipes
|| -zookeeper-recipes-election
|| -zookeeper-recipes-lock
\\ -zookeeper-recipes-queue
{noformat}
> Step 1.6 - Create zk-server maven structure
> ---
>
> Key: ZOOKEEPER-3032
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3032
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: build, scripts
>Affects Versions: 3.6.0
>Reporter: Norbert Kalmar
>Assignee: Norbert Kalmar
>Priority: Major
>
> Create a project structure that separates the different parts of ZooKeeper
> into a more meaningful packages for the future maven build.
> This should be done in iterations to limit the impact.
> * First iteration - safe changes including moving src/docs to zk-docs,
> creating zk-it empty directory. Build and conf directory remains unchanged.
> These changes also have minimum impact on PR’s.
> * Second iteration - move src/recipes to zk-recipes.
> * Third iteration - move src/contrib to zk-contrib.
> * Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
> * Fifth iteration - move jute under src directory
> * *Sixth iteration* - move src/java/main to zk-server, also separate client
> code from server code, move common files to zookeeper-common.
> {noformat}
> zookeeper
> | -bin
> | -conf
> | -jute
> | -zookeeper-client
> || -zookeeper-client-c
> || -zookeeper-client-java
> | -zookeeper-common
> | -zookeeper-contrib
> || -zookeeper-contrib-fatjar
> || -zookeeper-contrib-huebrowser
> || -zookeeper-contrib-loggraph
> || -zookeeper-contrib-monitoring
> || -zookeeper-contrib-rest
> || -zookeeper-contrib-zkfuse
> || -zookeeper-contrib-zkperl
> || -zookeeper-contrib-zkpython
> || -zookeeper-contrib-zktreeutil
> |\ -zookeeper-contrib-zooinspector
> | -zookeeper-docs
> | -zookeeper-it (integration tests)
[jira] [Updated] (ZOOKEEPER-3032) Step 1.6 - Create zk-server maven structure
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norbert Kalmar updated ZOOKEEPER-3032:
--
Description:
Create a project structure that separates the different parts of ZooKeeper into
a more meaningful packages for the future maven build.
This should be done in iterations to limit the impact.
* First iteration - safe changes including moving src/docs to zk-docs, creating
zk-it empty directory. Build and conf directory remains unchanged. These
changes also have minimum impact on PR’s.
* Second iteration - move src/recipes to zk-recipes.
* Third iteration - move src/contrib to zk-contrib.
* Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
* Fifth iteration - move jute under src directory
* *Sixth iteration* - move src/java/main to zk-server, which will be further
separated in Step 2.
{noformat}
zookeeper
| -bin
| -conf
| -jute
| -zookeeper-client
|| -zookeeper-client-c
|| -zookeeper-client-java
| -zookeeper-common
| -zookeeper-contrib
|| -zookeeper-contrib-fatjar
|| -zookeeper-contrib-huebrowser
|| -zookeeper-contrib-loggraph
|| -zookeeper-contrib-monitoring
|| -zookeeper-contrib-rest
|| -zookeeper-contrib-zkfuse
|| -zookeeper-contrib-zkperl
|| -zookeeper-contrib-zkpython
|| -zookeeper-contrib-zktreeutil
|\ -zookeeper-contrib-zooinspector
| -zookeeper-docs
| -zookeeper-it (integration tests)
| -zookeeper-server
| -zookeeper-recipes
|| -zookeeper-recipes-election
|| -zookeeper-recipes-lock
\\ -zookeeper-recipes-queue
{noformat}
was:
Create a project structure that separates the different parts of ZooKeeper into
a more meaningful packages for the future maven build.
This should be done in iterations to limit the impact.
* First iteration - safe changes including moving src/docs to zk-docs, creating
zk-it empty directory. Build and conf directory remains unchanged. These
changes also have minimum impact on PR’s.
* Second iteration - move src/recipes to zk-recipes.
* Third iteration - move src/contrib to zk-contrib.
* Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
* *Fifth iteration* - move src/java/main to zk-server, which will be further
separated in Step 2.
{noformat}
zookeeper
| -bin
| -conf
| -jute
| -zookeeper-client
|| -zookeeper-client-c
|| -zookeeper-client-java
| -zookeeper-common
| -zookeeper-contrib
|| -zookeeper-contrib-fatjar
|| -zookeeper-contrib-huebrowser
|| -zookeeper-contrib-loggraph
|| -zookeeper-contrib-monitoring
|| -zookeeper-contrib-rest
|| -zookeeper-contrib-zkfuse
|| -zookeeper-contrib-zkperl
|| -zookeeper-contrib-zkpython
|| -zookeeper-contrib-zktreeutil
|\ -zookeeper-contrib-zooinspector
| -zookeeper-docs
| -zookeeper-it (integration tests)
| -zookeeper-server
| -zookeeper-recipes
|| -zookeeper-recipes-election
|| -zookeeper-recipes-lock
\\ -zookeeper-recipes-queue
{noformat}
> Step 1.6 - Create zk-server maven structure
> ---
>
> Key: ZOOKEEPER-3032
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3032
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: build, scripts
>Affects Versions: 3.6.0
>Reporter: Norbert Kalmar
>Assignee: Norbert Kalmar
>Priority: Major
>
> Create a project structure that separates the different parts of ZooKeeper
> into a more meaningful packages for the future maven build.
> This should be done in iterations to limit the impact.
> * First iteration - safe changes including moving src/docs to zk-docs,
> creating zk-it empty directory. Build and conf directory remains unchanged.
> These changes also have minimum impact on PR’s.
> * Second iteration - move src/recipes to zk-recipes.
> * Third iteration - move src/contrib to zk-contrib.
> * Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
> * Fifth iteration - move jute under src directory
> * *Sixth iteration* - move src/java/main to zk-server, which will be further
> separated in Step 2.
> {noformat}
> zookeeper
> | -bin
> | -conf
> | -jute
> | -zookeeper-client
> || -zookeeper-client-c
> || -zookeeper-client-java
> | -zookeeper-common
> | -zookeeper-contrib
> || -zookeeper-contrib-fatjar
> || -zookeeper-contrib-huebrowser
> || -zookeeper-contrib-loggraph
> || -zookeeper-contrib-monitoring
> || -zookeeper-contrib-rest
> || -zookeeper-contrib-zkfuse
> || -zookeeper-contrib-zkperl
> || -zookeeper-contrib-zkpython
> || -zookeeper-contrib-zktreeutil
> |\ -zookeeper-contrib-zooinspector
> | -zookeeper-docs
> | -zookeeper-it (integration tests)
> | -zookeeper-server
> | -zookeeper-recipes
> || -zookeeper-recipes-election
> || -zookeeper-recipes-lock
> \\
[jira] [Updated] (ZOOKEEPER-3032) Step 1.6 - Create zk-server maven structure
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norbert Kalmar updated ZOOKEEPER-3032:
--
Summary: Step 1.6 - Create zk-server maven structure (was: Step 1.5 -
Create zk-server maven structure)
> Step 1.6 - Create zk-server maven structure
> ---
>
> Key: ZOOKEEPER-3032
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3032
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: build, scripts
>Affects Versions: 3.6.0
>Reporter: Norbert Kalmar
>Assignee: Norbert Kalmar
>Priority: Major
>
> Create a project structure that separates the different parts of ZooKeeper
> into a more meaningful packages for the future maven build.
> This should be done in iterations to limit the impact.
> * First iteration - safe changes including moving src/docs to zk-docs,
> creating zk-it empty directory. Build and conf directory remains unchanged.
> These changes also have minimum impact on PR’s.
> * Second iteration - move src/recipes to zk-recipes.
> * Third iteration - move src/contrib to zk-contrib.
> * Fourth iteration - move src/c to zk-client (java will be moved in Phase 2)
> * *Fifth iteration* - move src/java/main to zk-server, which will be further
> separated in Step 2.
> {noformat}
> zookeeper
> | -bin
> | -conf
> | -jute
> | -zookeeper-client
> || -zookeeper-client-c
> || -zookeeper-client-java
> | -zookeeper-common
> | -zookeeper-contrib
> || -zookeeper-contrib-fatjar
> || -zookeeper-contrib-huebrowser
> || -zookeeper-contrib-loggraph
> || -zookeeper-contrib-monitoring
> || -zookeeper-contrib-rest
> || -zookeeper-contrib-zkfuse
> || -zookeeper-contrib-zkperl
> || -zookeeper-contrib-zkpython
> || -zookeeper-contrib-zktreeutil
> |\ -zookeeper-contrib-zooinspector
> | -zookeeper-docs
> | -zookeeper-it (integration tests)
> | -zookeeper-server
> | -zookeeper-recipes
> || -zookeeper-recipes-election
> || -zookeeper-recipes-lock
> \\ -zookeeper-recipes-queue
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
