[
https://issues.apache.org/jira/browse/CALCITE-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568891#comment-16568891
]
Michael Mior commented on CALCITE-2442:
---------------------------------------
Finally got it. For some reason it completely slipped my mind that stack traces
were truncated. It turns out the bug is in jamm which fails to parse JVM
versions without a dot. This was fixed in version 0.3.2, but currently 0.3.0 is
being used by the embedded Cassandra instance. Overriding the version fixes
things for me.
> Cassandra unit test leaves stale folders in cassandra/ module on Windows
> ------------------------------------------------------------------------
>
> Key: CALCITE-2442
> URL: https://issues.apache.org/jira/browse/CALCITE-2442
> Project: Calcite
> Issue Type: Bug
> Components: cassandra
> Reporter: Andrei Sereda
> Priority: Major
>
> [~Sergey Nuyanzin] reported that
> [CassandraUnit|https://github.com/jsevellec/cassandra-unit] leaves
> {{.toDelete}} folder in maven module folder ({{cassandra/}}) rather than
> {{target/}} where all build and temporary files should be located.
> {quote}
> There is one more strange thing (at least on Windows): while building a
> file with name ".toDelete" is generated under calcite\cassandra and it's
> not removed by the end of tests
> Is there a way to make cassandra generates these files in target directory
> e.g.?
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
