You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2013/09/12 18:08:52 UTC

[jira] [Updated] (CASSANDRA-6015) Update version in build.xml to reflect 2.1

     [ https://issues.apache.org/jira/browse/CASSANDRA-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McGuire updated CASSANDRA-6015:
------------------------------------

    Description: 
The build.xml still marks the base.version as 2.0.0 in trunk.

This [breaks ccm|https://github.com/pcmanus/ccm/issues/73], as it's checking for this version number when it's doing things with 2.1 features (like logback logging, instead of log4j)


  was:
The build.xml still marks the base.version as 2.0.0 in trunk.

This breaks ccm, as it's checking for this version number when it's doing things with 2.1 features (like logback logging, instead of log4j)


    
> Update version in build.xml to reflect 2.1
> ------------------------------------------
>
>                 Key: CASSANDRA-6015
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6015
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ryan McGuire
>            Priority: Trivial
>
> The build.xml still marks the base.version as 2.0.0 in trunk.
> This [breaks ccm|https://github.com/pcmanus/ccm/issues/73], as it's checking for this version number when it's doing things with 2.1 features (like logback logging, instead of log4j)

--
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