[
https://issues.apache.org/jira/browse/ZOOKEEPER-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norbert Kalmar updated ZOOKEEPER-3031:
--------------------------------------
Description:
After moving to maven build is completed, ZooKeeper artifacts should be
published to the Maven Central repository.
There should be a different artifact for client code only, so that components
that only require the client doesn't have to have the whole ZooKeeper as a
dependency.
was:
Create a project structure that separates the different parts of ZooKeeper into
a more meaningful packages for the future maven build.
This first step should not impact Jenkins QA.
{noformat}
zookeeper
|-bin
|-conf
|-zk-client
| |-zk-client-c
|-zk-contrib
| |-zk-contrib-fatjar
| |-zk-contrib-huebrowser
| |-zk-contrib-loggraph
| |-zk-contrib-monitoring
| |-zk-contrib-rest
| |-zk-contrib-zkfuse
| |-zk-contrib-zkperl
| |-zk-contrib-zkpython
| |-zk-contrib-zktreeutil
| \-zk-contrib-zooinspector
|-zk-docs
|-zk-it (integration tests)
|-zk-server
|-zk-recipes
| |-zk-recipes-election
| |-zk-recipes-lock
\ \-zk-recipes-queue
{noformat}
> Publish artifacts to Maven Central repo
> ---------------------------------------
>
> Key: ZOOKEEPER-3031
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3031
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: build, scripts
> Affects Versions: 3.6.0
> Reporter: Norbert Kalmar
> Assignee: Norbert Kalmar
> Priority: Major
>
> After moving to maven build is completed, ZooKeeper artifacts should be
> published to the Maven Central repository.
> There should be a different artifact for client code only, so that components
> that only require the client doesn't have to have the whole ZooKeeper as a
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
