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

Andres de la Peña commented on CASSANDRA-17014:
-----------------------------------------------

Committed to 3.0 as 
[0c4653110d80f411d2c50445d48478967bcaa095|https://github.com/apache/cassandra/commit/0c4653110d80f411d2c50445d48478967bcaa095]and
 merged up to 
[3.11|https://github.com/apache/cassandra/commit/2614f7eeb4343b1d752a16688a1dc55ab245ca8f],
 
[4.0|https://github.com/apache/cassandra/commit/36266ce257e62b74a1e68aadba637b2dc75b32fc]
 and 
[trunk|https://github.com/apache/cassandra/commit/bcdb575fd32bccf196c8b398c7bb9f95f2591b73].

> Make -Dtest.methods optional in all Ant test targets
> ----------------------------------------------------
>
>                 Key: CASSANDRA-17014
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17014
>             Project: Cassandra
>          Issue Type: Task
>          Components: Build
>            Reporter: Andres de la Peña
>            Assignee: Andres de la Peña
>            Priority: Low
>
> The Ant build file contains several targets to run specific tests:
>  * testsome
>  * long-testsome
>  * burn-testsome
>  * cql-test-some
>  * stress-test-some
>  * test-jvm-dtest-some
> These targets take two arguments, {{test.name}} and {{test.methods}}. The 
> first argument, {{test.name}}, is always mandatory. However, {{test.methods}} 
> can be either mandatory or optional depending on the target and the project 
> branch. For example, in {{testsome}} the argument is mandatory in 3.0 and 
> 3.11 and optional in 4.0 and trunk. Also, in trunk {{test.methods}} is 
> optional for all the targets except {{cql-test-some}}.
> The purpose of this ticket is making {{test.methods}} consistently optional 
> for all the {{*some}} targets.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to