[ https://issues.apache.org/jira/browse/CURATOR-429?focusedWorklogId=241222&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241222 ]
ASF GitHub Bot logged work on CURATOR-429: ------------------------------------------ Author: ASF GitHub Bot Created on: 13/May/19 18:27 Start Date: 13/May/19 18:27 Worklog Time Spent: 10m Work Description: oscerd commented on issue #311: [CURATOR-429] Make Curator 4.x compatible with Zookeeper 3.4.x in OSGi too URL: https://github.com/apache/curator/pull/311#issuecomment-491934083 Without applying a version range the result is that curator will work only with zookeeper 3.5, because this the dependency declared in curator. It will use what is located in the POM. Relaxing the requirement by introducing a range is usually the best way to manage this situation. This will made true the sentence "curator can work with zookeeper 3.4 and 3.5, from version 4.x". Actually this is not true for OSGi container. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 241222) Time Spent: 50m (was: 40m) > Make Curator 4.x compatible with Zookeeper 3.4.x in OSGi too > ------------------------------------------------------------ > > Key: CURATOR-429 > URL: https://issues.apache.org/jira/browse/CURATOR-429 > Project: Apache Curator > Issue Type: Improvement > Affects Versions: 4.0.0 > Reporter: Andrea Cosentino > Assignee: Jordan Zimmerman > Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > Currently in OSGi curator need Zookeeper >= 3.5 to work. Maybe you can think > of relaxing this constraint by adding a version range. -- This message was sent by Atlassian JIRA (v7.6.3#76005)