Merging the surefire/failsafe site

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Merging the surefire/failsafe site

Kristian Rosenvold-4
Stephen,

You mentioned that you might find the time to merge the
surefire/failsafe sites into one site. I'm wondering if that'd be now ;)

I'm mostly concerned about getting the structure set up correctly and
all the links working and stuff like that.

Since I'm a real wiz at merging *files* I can actually do the content
merge itself for the docs, if you for instance start by
creating the unified site based on the surefire site I can track down
the diffs in the failsafe site. (Insert smug remark about
the power of git here --> <---).

Kristian





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

Reply | Threaded
Open this post in threaded view
|

Re: Merging the surefire/failsafe site

stephenconnolly
if you can get the parallel test execution, where each test case is farmed
out to a thread, not a thread per class, then we may have a deal.

chat later (after 9am gmt+1h) to discuss (irc or gtalk)

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 24 Jun 2011 07:34, "Kristian Rosenvold" <[hidden email]>
wrote:

> Stephen,
>
> You mentioned that you might find the time to merge the
> surefire/failsafe sites into one site. I'm wondering if that'd be now ;)
>
> I'm mostly concerned about getting the structure set up correctly and
> all the links working and stuff like that.
>
> Since I'm a real wiz at merging *files* I can actually do the content
> merge itself for the docs, if you for instance start by
> creating the unified site based on the surefire site I can track down
> the diffs in the failsafe site. (Insert smug remark about
> the power of git here --> <---).
>
> Kristian
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: Merging the surefire/failsafe site

Kristian Rosenvold-4
We can do that ;)

I've just created the "3.0" release in Jira (there is also a 2.10). I am
planning to start discussing which features/issues to include in such a
release. At the moment I'm just assigning some issues to 3.0. Most of
the hard stuff for doing what you want was already done in 2.9, which
now includes most of the plumbing for a fully operational 2 way comms
channel between the plugin and the fork. This would quite easily allow
options like forkMode="perThread" and reuseFork="true/false".

So why don't you just create the issue and assign it to 3.0, just before
you start consolidating the site ;)


Kristian




Den 24.06.2011 09:36, skrev Stephen Connolly:

> if you can get the parallel test execution, where each test case is farmed
> out to a thread, not a thread per class, then we may have a deal.
>
> chat later (after 9am gmt+1h) to discuss (irc or gtalk)
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
> On 24 Jun 2011 07:34, "Kristian Rosenvold"<[hidden email]>
> wrote:
>> Stephen,
>>
>> You mentioned that you might find the time to merge the
>> surefire/failsafe sites into one site. I'm wondering if that'd be now ;)
>>
>> I'm mostly concerned about getting the structure set up correctly and
>> all the links working and stuff like that.
>>
>> Since I'm a real wiz at merging *files* I can actually do the content
>> merge itself for the docs, if you for instance start by
>> creating the unified site based on the surefire site I can track down
>> the diffs in the failsafe site. (Insert smug remark about
>> the power of git here -->  <---).
>>
>> Kristian
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>


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

Reply | Threaded
Open this post in threaded view
|

Re: Merging the surefire/failsafe site

stephenconnolly
Done.

http://jira.codehaus.org/browse/SUREFIRE-751

On 24 June 2011 09:21, Kristian Rosenvold <[hidden email]>wrote:

> We can do that ;)
>
> I've just created the "3.0" release in Jira (there is also a 2.10). I am
> planning to start discussing which features/issues to include in such a
> release. At the moment I'm just assigning some issues to 3.0. Most of the
> hard stuff for doing what you want was already done in 2.9, which now
> includes most of the plumbing for a fully operational 2 way comms channel
> between the plugin and the fork. This would quite easily allow options like
> forkMode="perThread" and reuseFork="true/false".
>
> So why don't you just create the issue and assign it to 3.0, just before
> you start consolidating the site ;)
>
>
> Kristian
>
>
>
>
> Den 24.06.2011 09:36, skrev Stephen Connolly:
>
>  if you can get the parallel test execution, where each test case is farmed
>> out to a thread, not a thread per class, then we may have a deal.
>>
>> chat later (after 9am gmt+1h) to discuss (irc or gtalk)
>>
>> - Stephen
>>
>> ---
>> Sent from my Android phone, so random spelling mistakes, random nonsense
>> words and other nonsense are a direct result of using swype to type on the
>> screen
>> On 24 Jun 2011 07:34, "Kristian Rosenvold"<kristian.rosenvold@**gmail.com<[hidden email]>
>> >
>> wrote:
>>
>>> Stephen,
>>>
>>> You mentioned that you might find the time to merge the
>>> surefire/failsafe sites into one site. I'm wondering if that'd be now ;)
>>>
>>> I'm mostly concerned about getting the structure set up correctly and
>>> all the links working and stuff like that.
>>>
>>> Since I'm a real wiz at merging *files* I can actually do the content
>>> merge itself for the docs, if you for instance start by
>>> creating the unified site based on the surefire site I can track down
>>> the diffs in the failsafe site. (Insert smug remark about
>>> the power of git here -->  <---).
>>>
>>> Kristian
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: [hidden email].**org<[hidden email]>
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: [hidden email].**org<[hidden email]>
> For additional commands, e-mail: [hidden email]
>
>