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

Nate McCall edited comment on CASSANDRA-636 at 12/17/09 2:10 AM:
-----------------------------------------------------------------

Sorry if that patch file is a little confusing - I just realized I yanked an 
unused import from src/java/org/apache/cassandra/cli/CliClient.java as well. 
Should I create a new issue for this and attach separately? Please advise, I'm 
a little new at this. 
edit: just created CASSANDRA-637 for the CliClient import.

      was (Author: zznate):
    Sorry if that patch file is a little confusing - I just realized I yanked 
an unused import from src/java/org/apache/cassandra/cli/CliClient.java as well. 
Should I create a new issue for this and attach separately? Please advise, I'm 
a little new at this.
  
> SSTableImportTest is looking for test resources that are not available via 
> the pom
> ----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-636
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-636
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Nate McCall
>         Attachments: patch
>
>
> Trying to run 'mvn test' and a fresh checkout of the 5.0 branch results in a 
> failure of org.apache.cassandra.tools.SSTableImportTest
> The test resources are currently located in [basedir]/test/resources yet 
> there is no <testResources> directive to include such in the pom. The 
> following patch includes a fix to the test case for looking in the top-level 
> of the classpath as well as a fix to the pom for including these resources.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to