maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Lundberg <denn...@apache.org>
Subject Re: svn commit: r1049118 - in /maven/surefire/trunk: maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/ maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/ maven-surefire-common/src/main/java/org/apache/maven/plugin/sur...
Date Tue, 14 Dec 2010 22:44:30 GMT
On 2010-12-14 20:03, Kristian Rosenvold wrote:
> The way I understand you this is halfway a documentation issue; any
> non-legal value including the string "filesystem" will actually give you
> filesystem order.
> 
> So I could "solve" this by just adding "filesystem" to the list of legal
> options, right ?
> 
> Another issue is that Dennis actually converted the default value to
> "alphabetical" in his original fix. When introducing more options I
> reverted to the old-style behaviour as default (filesystem).

That's good. It didn't occur to me at the time to make it configurable.

> Actually changing the default order will break some people's tests, but
> I have a marginal preference for alphabetical. But it's sufficiently
> marginal taht I prefer compatibility ;)

Me too

> KRistian
> 
> 
> ti., 14.12.2010 kl. 17.32 +0100, skrev Benjamin Bentmann:
>> Hi Kristian,
>>
>>> Author: krosenvold
>>> Date: Tue Dec 14 14:55:52 2010
>>> New Revision: 1049118
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1049118&view=rev
>>> Log:
>>> [SUREFIRE-321] Added runOrder mojo attribute, including documentation.
>>> [...]
>>> @@ -595,6 +595,20 @@ public class IntegrationTestMojo
>>>       private Boolean parallelMavenExecution;
>>>
>>>       /**
>>> +      * Defines the order the tests will be run in. Supported values are alphabetical,
reversealphabetical
>>> +      * random, hourly (alphabetical on even hours, reverse alphabetical on
odd hours).
>>> +      *
>>> +      * Not supplying a value for this setting will run tests in filesystem
order.
>>> +      *
>>> +      * Odd/Even is determined at the time the of scanning the classpath, meaning
it could change during
>>> +      * a multi-module build.
>>> +      *
>>> +      * @parameter
>>> +      * @since 2.7
>>> +      */
>>> +     private String runOrder;
>>
>> Should there be an explicit value for the filesystem order? I'm thinking 
>> about a parent POM where runOrder gets set to say hourly but a child 
>> project wants to stick with the (current) filesystem order.
>>
>>
>> Benjamin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message