[
https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923516#action_12923516
]
Doug Cutting commented on ZOOKEEPER-102:
Avro is not wire-compatible with Jute
[
https://issues.apache.org/jira/browse/ZOOKEEPER-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12752752#action_12752752
]
Doug Cutting commented on ZOOKEEPER-521:
This is not required. Many Apache
[
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723211#action_12723211
]
Doug Cutting commented on ZOOKEEPER-224:
why do we need ivy?
Ivy seems
[
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723257#action_12723257
]
Doug Cutting commented on ZOOKEEPER-224:
but for the specific issue of getting
+1
I note that 'ant clean test' fails, since the build requires an svn
checkout, but 'ant test' on a release succeeds. It would be best if the
build worked without a subversion checkout. But that's a nit.
Doug
Patrick Hunt wrote:
I've created a second candidate build for ZooKeeper 3.0.1.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650636#action_12650636
]
Doug Cutting commented on ZOOKEEPER-224:
Shouldn't the pom metadata files
[
https://issues.apache.org/jira/browse/ZOOKEEPER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650766#action_12650766
]
Doug Cutting commented on ZOOKEEPER-233:
Why not generate two disjoint jar files
[
https://issues.apache.org/jira/browse/ZOOKEEPER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650814#action_12650814
]
Doug Cutting commented on ZOOKEEPER-233:
I think the more common thing
+1
The release looks great, much better than most first releases!
I noticed a few minor problems in the documentation, but these should by
no means not stop the release. In particular:
- The Zookeeper Documentation tab should contain the version number.
- Informal Documentation might
[
https://issues.apache.org/jira/browse/ZOOKEEPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620337#action_12620337
]
Doug Cutting commented on ZOOKEEPER-110:
The exec task will fail on Windows
[
https://issues.apache.org/jira/browse/ZOOKEEPER-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12619975#action_12619975
]
Doug Cutting commented on ZOOKEEPER-103:
On ZOOKEEPER-83 we plainly agreed
[
https://issues.apache.org/jira/browse/ZOOKEEPER-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12619111#action_12619111
]
Doug Cutting commented on ZOOKEEPER-103:
The maven convention is to have each
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615799#action_12615799
]
Doug Cutting commented on ZOOKEEPER-83:
---
Is that the only issue?
I think its
[
https://issues.apache.org/jira/browse/ZOOKEEPER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614466#action_12614466
]
Doug Cutting commented on ZOOKEEPER-80:
---
Whoa! Big issue description! Perhaps you
Patrick Hunt wrote:
We were thinking of contrib as interesting stuff that users might want
to re-use/share but not core to zookeeper, we'll carry it around so that
users know where to find it, if it gets broken and no one fixes it it
won't hold up the release
That's a fine policy for
15 matches
Mail list logo