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 (Commented) (JIRA)" <ji...@apache.org> on 2011/11/30 19:09:40 UTC

[jira] [Commented] (ZOOKEEPER-1311) Zookeeper test jar is broken

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

Patrick Hunt commented on ZOOKEEPER-1311:
-----------------------------------------

As part of fixing this it would be great to have something we could use to validate ZK deployment to the maven repo as part of the release process. Mahadev and I tested this ourselves, but didn't notice the test issue.
                
> Zookeeper test jar is broken
> ----------------------------
>
>                 Key: ZOOKEEPER-1311
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1311
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: Ivan Kelly
>            Priority: Blocker
>             Fix For: 3.5.0, 3.4.1
>
>
> In http://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.0/ the test jar cannot be accessed by maven. 
> There are two possible solutions to this. 
> a) rename zookeeper-3.4.0-test.jar to zookeeper-3.4.0-tests.jar and remove zookeeper-3.4.0-test.pom*
> With this, the maven can access the test jar with
> {code}
>      <dependency>
>        <groupId>org.apache.zookeeper</groupId>
>        <artifactId>zookeeper</artifactId>
>        <version>3.4.0</version>
>        <type>test-jar</type>
>        <scope>test</scope>
>      </dependency>
> {code}
> b) Alternatively, zookeeper test could be it's own submodule. To do this, it must be deployed in the following layout
> {code}
> ./org/apache/zookeeper/zookeeper-test/3.4.0-BK-SNAPSHOT/zookeeper-test-3.4.0.jar
> ./org/apache/zookeeper/zookeeper-test/3.4.0-BK-SNAPSHOT/zookeeper-test-3.4.0.jar.md5
> ./org/apache/zookeeper/zookeeper-test/3.4.0-BK-SNAPSHOT/zookeeper-test-3.4.0.jar.sha1
> ./org/apache/zookeeper/zookeeper-test/3.4.0-BK-SNAPSHOT/zookeeper-test-3.4.0.pom
> ./org/apache/zookeeper/zookeeper-test/3.4.0-BK-SNAPSHOT/zookeeper-test-3.4.0.pom.md5
> ./org/apache/zookeeper/zookeeper-test/3.4.0-BK-SNAPSHOT/zookeeper-test-3.4.0.pom.sha1
> {code}
> This can then be accessed by maven with
> {code}
>      <dependency>
>        <groupId>org.apache.zookeeper</groupId>
>        <artifactId>zookeeper-test</artifactId>
>        <version>3.4.0</version>
>        <scope>test</scope>
>      </dependency>
> {code}
> I think a) is the better solution.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira