Update project.clj - Bump snakeyaml dependency version from 1.9 to 1.11 (Latest Release) #567

Merged
merged 1 commit into from Jul 9, 2013

Projects

None yet

3 participants

@kb
Contributor
kb commented May 9, 2013

Storm is using a snakeyaml version that is now two revisions old. I have recently come across a dependency conflict when using Storm with JRuby 1.7.3. When running in ruby 1.9 mode JRuby utilizes the snakeyaml library, however the internal JRuby version of snakeyaml 1.11. Since Storm is running an outdated version, it would make sense to propose the change in hopes of resolving this dependency conflict.

@kb kb Update project.clj - Bump snakeyaml dependency version from 1.9 to 1.…
…11 (Latest Release)

Storm is using a snakeyaml version that is now two revisions old. I have recently come across a dependency conflict when using Storm with JRuby 1.7.3. When running in ruby 1.9 mode JRuby utilizes the snakeyaml library, however the internal JRuby  version of snakeyaml 1.11. Since Storm is running an outdated version, it would make sense to propose the change in hopes of resolving this dependency conflict.
b259294
@colinsurprenant

+1

JRuby 1.7.3, which will be included in the upcoming RedStorm release, uses snakeyaml 1.11.

We cannot downgrade snakeyaml to 1.9 in the topology jar - when running a topology that uses the JRuby YAML api, it crashes on org.yaml.snakeyaml.events.DocumentStartEvent.getVersion() which returns an Integer object in 1.9 and a DumperOptions$Version object in 1.11.

Upgrading snakeyaml to 1.11 in Storm 0.8.2 has solved the problem and basic/test topologies are working well. I haven't done any further analysis & tests in Storm to verify potential problems with this upgrade.

@nathanmarz nathanmarz merged commit cb45c17 into nathanmarz:master Jul 9, 2013
@bridiver bridiver added a commit to korrelate/storm that referenced this pull request Dec 1, 2013
@bridiver bridiver upgrade snakeyaml for nathanmarz#567 1b08fa4
@bridiver bridiver referenced this pull request Dec 2, 2013
Closed

0.9.0 #762

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment