You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/01/15 05:59:00 UTC

[jira] [Commented] (ZOOKEEPER-3122) Verify build after maven migration and the end artifact

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742775#comment-16742775 ] 

Hudson commented on ZOOKEEPER-3122:
-----------------------------------

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #351 (See [https://builds.apache.org/job/ZooKeeper-trunk/351/])
ZOOKEEPER-3122: MAVEN MIGRATION - - remove contrib build from default (andor: rev b66802ef2f24181a3967152782d1cc8bb7886f35)
* (edit) pom.xml


> Verify build after maven migration and the end artifact
> -------------------------------------------------------
>
>                 Key: ZOOKEEPER-3122
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3122
>             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
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> This step should be done after every step, but especially before step 2, after moving all the directories to maven structure, the build directory should be verified that: 
> - Same jar files are created
> -- find build/ -name \*.jar
> --- jar tf build/zookeeper-3.6.0-SNAPSHOT-javadoc.jar 
> --- ...
> - Files available did not change, only their path:
> -- find build/ -type f | sort -k 2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)