Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of garydgregory@gmail.com
 designates 209.85.210.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAE9L6G18ihxZrDJg4x2yMNDRmMiFAz_K0DiXkaBMOtx0zE=GDg@mail.gmail.com>
References: 
 <CABeJX=2ZOxDF8Jm49y5nsnzvQ_HYhivQ2bw1j5=5y894uSDPrA@mail.gmail.com>
	<CAE9L6G0Ni2_5ut9b6M=iZD1nCV1ao8-n9BmN8X6r4+FrG4V2WQ@mail.gmail.com>
	<CACZkXPyZy_UhHtXrHouHtLZEW_ozorSJijioPuuV38DkAD-+zA@mail.gmail.com>
	<CABeJX=36J8wMP9NrR4UEDOLXa_ade2a16Nh4LmtddNZxgGSQ4A@mail.gmail.com>
	<CABeJX=3qXEGshXRTeJJhoXe=CP55v1pWxWMJdcNX4fgjR5sp9g@mail.gmail.com>
	<CAE9L6G18ihxZrDJg4x2yMNDRmMiFAz_K0DiXkaBMOtx0zE=GDg@mail.gmail.com>
Date: Mon, 17 Sep 2012 14:39:19 -0400
Message-ID: 
 <CACZkXPz3qPGVO+rpRO9HdXaQPShAP3_tMMHqyCpSAVJK+x8XhA@mail.gmail.com>
Subject: Re: [lang] Etiquette regarding updating test classes to use JUnit 4
 annotations
From: Gary Gregory <garydgregory@gmail.com>
To: Commons Developers List <dev@commons.apache.org>, gudnabrsam@gmail.com
Content-Type: multipart/alternative; boundary=e89a8ff1c9a26fc22e04c9ea1765

--e89a8ff1c9a26fc22e04c9ea1765
Content-Type: text/plain; charset=UTF-8

On Mon, Sep 17, 2012 at 2:27 PM, Matt Benson <gudnabrsam@gmail.com> wrote:

> On Mon, Sep 17, 2012 at 1:19 PM, Duncan Jones <duncan@wortharead.com>
> wrote:
> > On 17 September 2012 19:13, Duncan Jones <duncan@wortharead.com> wrote:
> >> On 17 September 2012 19:07, Gary Gregory <garydgregory@gmail.com>
> wrote:
> >>> On Mon, Sep 17, 2012 at 2:03 PM, Matt Benson <gudnabrsam@gmail.com>
> wrote:
> >>>
> >>>> Hello,
> >>>>   We'd love to have our whole testsuite updated to JUnit 4, IMO.  The
> >>>> only thing is that as a rule we'd rather that changeset be separate
> >>>> from another, so I'd recommend providing multiple patches, possibly
> >>>> submitted in separate JIRA issues.
> >>>>
> >>>
> >>> +1!
> >>>
> >>> Patch 1: Update to JUnit 4
> >>> Patch 2: the patch
> >>
> >> No problem, I like that approach.
> >
> > On second thought, how would I best accomplish this? If I create a
> > patch after converting the test case, then create another patch after
> > fixing the issue, the latter patch will contain the changes from the
> > first patch. Is this ok with everyone? Or is there some patch
> > difference tool I should know about?
> >
>

Git can help I suppose... But, I'd rather deal with these patches in two
themes in this case, JUnit 4 and then whatever comes next. If we are going
to spend time on JUnit 4, let's get in that mode, get it done and then move
on to other kinds of patches.

I do not plan on spending time teasing out a git patch on top of another
that clashes with something in SVN trunk.

Gary

>
> Good point.  I haven't played with it yet, but our github clone might
> provide some traction here.
>
> Matt
>
> > Duncan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--e89a8ff1c9a26fc22e04c9ea1765--