cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Coverston (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3506) cassandra.bat does not use SETLOCAL, can cause classpath issues
Date Fri, 18 Nov 2011 19:26:51 GMT

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

Benjamin Coverston commented on CASSANDRA-3506:
-----------------------------------------------

Reviewed patch +1.
                
> 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
>         Attachments: 3506.txt
>
>
> 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

        

Mime
View raw message