[
https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785697#comment-13785697
]
Patrick Hunt commented on ZOOKEEPER-1430:
-----------------------------------------
[~gkesavan] am I right in thinking this can be tested at any time (staging),
e.g. prior to committing for instance. We'd just drop the tests prior to the
release? Can you shed more light.
> add maven deploy support to the build
> -------------------------------------
>
> Key: ZOOKEEPER-1430
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430
> Project: ZooKeeper
> Issue Type: Task
> Components: build
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Priority: Blocker
> Fix For: 3.4.6, 3.5.0
>
> Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch,
> ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH
>
>
> Infra is phasing out the current mechanism we use to deploy maven artifacts.
> We need to move to repository.apache.org (nexus).
> In particular we need to ensure the following artifacts get published:
> * zookeeper-3.x.y.jar
> * zookeeper-3.x.y-sources.jar
> * zookeeper-3.x.y-tests.jar
> * zookeeper-3.x.y-javadoc.jar
> In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream
> users, such as Hadoop.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
