You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nate McCall (JIRA)" <ji...@apache.org> on 2009/12/17 03:05:18 UTC
[jira] Commented: (CASSANDRA-636) SSTableImportTest has a bad
import and is looking for resources that are not available
[ https://issues.apache.org/jira/browse/CASSANDRA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791735#action_12791735 ]
Nate McCall commented on CASSANDRA-636:
---------------------------------------
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 has a bad import and is looking for resources that are not available
> --------------------------------------------------------------------------------------
>
> 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.