You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jinder Aujla (JIRA)" <ji...@apache.org> on 2013/08/21 20:12:00 UTC

[jira] [Commented] (CASSANDRA-5917) NoSuchMethodError when calling YamlConfigurationLoader.loadConfig()

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

Jinder Aujla commented on CASSANDRA-5917:
-----------------------------------------

The build.xml:

https://github.com/apache/cassandra/blob/cassandra-2.0.0-rc1/build.xml

seems to point to version 1.6 of snakeyaml
                
> NoSuchMethodError when calling YamlConfigurationLoader.loadConfig()
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-5917
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5917
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>         Environment: Linux
>            Reporter: Jinder Aujla
>            Assignee: Dave Brosius
>            Priority: Minor
>
> Hi, when this method is called, I see this:
> java.lang.NoSuchMethodError: org.yaml.snakeyaml.Yaml.<init>(Lorg/yaml/snakeyaml/constructor/BaseConstructor;)V
> 	at org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:86)
> 	at org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:125)
> 	at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:101)
> ......
> I believe it's because of an enhancement made in ticket CASSANDRA-5606. The version of snakeyaml that 2.0.0-rc1 depends on is 1.6, but this constructor doesn't exist in that version but it does in version 1.12.
> Coincidentally CASSANDRA-5317 speaks of upgrading the snakeyaml dependency, but I'm not sure what was upgraded. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira