You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2013/12/03 02:13:36 UTC
[jira] [Comment Edited] (ZOOKEEPER-1430) add maven deploy support
to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837188#comment-13837188 ]
Patrick Hunt edited comment on ZOOKEEPER-1430 at 12/3/13 1:12 AM:
------------------------------------------------------------------
Thanks [~gkesavan]. Unfortunately the "ant clean package" build is now failing though:
{noformat}
BUILD FAILED
/home/phunt/dev/svn/svn-zookeeper/build.xml:745: Could not find file /home/phunt/dev/svn/svn-zookeeper/build/zookeeper-3.5.0-SNAPSHOT/dist-maven/zookeeper-3.5.0-SNAPSHOT.pom to generate checksum for.
{noformat}
Could you take a look? Thanks.
Also a question - why do we end up with 4 copies of the pom file in the snapshot repo (repository.apache.org), rather than a single (as we do for each of the jars). afaict all the poms are the same, just we have four copies. Can we address that? Is it going to be an issue when staging/releasing? Is there some way you can address this, just have one pom rather than 4 copies?
was (Author: phunt):
Thanks [~gkesavan]. Unfortunately the "ant clean package" build is now failing though:
{noformat}
BUILD FAILED
/home/phunt/dev/svn/svn-zookeeper/build.xml:745: Could not find file /home/phunt/dev/svn/svn-zookeeper/build/zookeeper-3.5.0-SNAPSHOT/dist-maven/zookeeper-3.5.0-SNAPSHOT.pom to generate checksum for.
{noformat}
Could you take a look? Thanks.
Also a question - why do we end up with 4 copies of the pom file in the snapshot repo, rather than a single (as we do for each of the jars). afaict all the poms are the same, just we have four copies. Can we address that? Is it going to be an issue when staging/releasing? Is there some way you can address this, just have one pom rather than 4 copies?
> 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.patch, ZOOKEEPER-1430-3.5.0-v4.patch, ZOOKEEPER-1430-3.5.0-v5.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#6144)