[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build

["Giridharan Kesavan (JIRA)" <ji...@apache.org>]

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

Giridharan Kesavan updated ZOOKEEPER-1430:
------------------------------------------

    Attachment: ZOOKEEPER-1430-3.5.0-v6.patch
                ZOOKEEPER-1430-3.4.6-v6.patch

[~phunt] ${final.name} is nothing but ${name}-${version} and by convention maven projects doesn't have pom file that are versioned. When publishing the pom.xml file maven by itself will figureout the version of the pom file and publish it. 

To answer your second question about multiple pom's. it's not b'coz of the pom name, it's bcoz the way the ant macro def call's the individual publish task. it consider's every deploy call as separate module and publishes the same pom file with different build number. 

With this v6 patch I have made it a single call and all the artifacts will be published at one go. 

I have tested the patch for clean package, mvn-deploy, and mvn-deploy the staging as well. 

> 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
>    Affects Versions: 3.4.4, 3.5.0
>            Reporter: Patrick Hunt
>            Assignee: Giridharan Kesavan
>            Priority: Blocker
>             Fix For: 3.4.6, 3.5.0
>
>         Attachments: ZOOKEEPER-1430-3.4.6-v4.patch, ZOOKEEPER-1430-3.4.6-v5.patch, ZOOKEEPER-1430-3.4.6-v6.patch, ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430-3.5.0-v4.patch, ZOOKEEPER-1430-3.5.0-v5.patch, ZOOKEEPER-1430-3.5.0-v6.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH, ZOOKEEPER-1430-V3.patch, ZOOKEEPER-1430-br34-V3.patch, ZOOKEEPER-1430.patch, ZOOKEEPER-1430.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.4#6159)