You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Ivan Kelly (Created) (JIRA)" <ji...@apache.org> on 2011/11/30 19:05:42 UTC
[jira] [Created] (ZOOKEEPER-1311) Zookeeper test jar is broken
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.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
[jira] [Updated] (ZOOKEEPER-1311) ZooKeeper test jar is broken
Posted by "Patrick Hunt (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-1311:
------------------------------------
Summary: ZooKeeper test jar is broken (was: Zookeeper test jar is broken)
> 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
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 3.5.0, 3.4.1
>
> Attachments: ZOOKEEPER-1311.diff
>
>
> 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
[jira] [Commented] (ZOOKEEPER-1311) ZooKeeper test jar is broken
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160808#comment-13160808 ]
Hudson commented on ZOOKEEPER-1311:
-----------------------------------
Integrated in ZooKeeper-trunk #1381 (See [https://builds.apache.org/job/ZooKeeper-trunk/1381/])
ZOOKEEPER-1311. ZooKeeper test jar is broken (Ivan Kelly via phunt)
phunt : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208979
Files :
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/build.xml
> 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
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 3.5.0, 3.4.1
>
> Attachments: ZOOKEEPER-1311.diff
>
>
> 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
[jira] [Assigned] (ZOOKEEPER-1311) Zookeeper test jar is broken
Posted by "Patrick Hunt (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt reassigned ZOOKEEPER-1311:
---------------------------------------
Assignee: Ivan Kelly
> 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
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 3.5.0, 3.4.1
>
> Attachments: ZOOKEEPER-1311.diff
>
>
> 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
[jira] [Commented] (ZOOKEEPER-1311) Zookeeper test jar is broken
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160231#comment-13160231 ]
Hadoop QA commented on ZOOKEEPER-1311:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505642/ZOOKEEPER-1311.diff
against trunk revision 1202557.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/800//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/800//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/800//console
This message is automatically generated.
> 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
>
> Attachments: ZOOKEEPER-1311.diff
>
>
> 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
[jira] [Commented] (ZOOKEEPER-1311) Zookeeper test jar is broken
Posted by "Patrick Hunt (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (ZOOKEEPER-1311) Zookeeper test jar is broken
Posted by "Ivan Kelly (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160207#comment-13160207 ]
Ivan Kelly commented on ZOOKEEPER-1311:
---------------------------------------
It could be tested with a pom.xml that pulls in the different parts. I don't know how to automate that testing though.
> 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
[jira] [Updated] (ZOOKEEPER-1311) Zookeeper test jar is broken
Posted by "Patrick Hunt (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-1311:
------------------------------------
Fix Version/s: 3.5.0
> 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
[jira] [Updated] (ZOOKEEPER-1311) Zookeeper test jar is broken
Posted by "Ivan Kelly (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Kelly updated ZOOKEEPER-1311:
----------------------------------
Attachment: ZOOKEEPER-1311.diff
> 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
>
> Attachments: ZOOKEEPER-1311.diff
>
>
> 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