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

Posted to commits@cassandra.apache.org by "Tyler Hobbs (Assigned) (JIRA)" <ji...@apache.org> on 2011/11/18 20:08:51 UTC

[jira] [Assigned] (CASSANDRA-3506) cassandra.bat does not use SETLOCAL, can cause classpath issues

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

Tyler Hobbs reassigned CASSANDRA-3506:
--------------------------------------

    Assignee: Tyler Hobbs
    
> cassandra.bat does not use SETLOCAL, can cause classpath issues
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-3506
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3506
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.2
>         Environment: Windows
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>            Priority: Minor
>
> In bin/cassandra.bat, we don't use SETLOCAL (although we do use ENDLOCAL for some reason), so modifications to the classpath within the batch script persist.  This means that if you run cassandra-1.0.0/bin/cassandra.bat, kill the process, and then run cassandra-1.0.3/bin/cassandra.bat, the 1.0.0 jars will still be in the classpath. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira