Forgive the top post. In case anybody hasn't figured
it out, with Ant 1.7 beta 2 out the door and a new
AntUnit 1.0 beta apparently hot on its heels, I am
working on modifying the Ant core build to run both
junit and antunit tests... just to make sure nobody's
duplicating work. I am basically do
Forgive the top post. In case anybody hasn't figured
it out, with Ant 1.7 beta 2 out the door and a new
AntUnit 1.0 beta apparently hot on its heels, I am
working on modifying the Ant core build to run both
junit and antunit tests... just to make sure nobody's
duplicating work. I am basically doi
On Thu, 14 Sep 2006, Matt Benson <[EMAIL PROTECTED]> wrote:
> --- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>> I didn't think of the *-support.xml case, that would
>> need to be added.
>
> This is the only contention area, then.
Wouldn't call it contention. I just didn't think of the case where
Trying to resend, since bounced. --DD
On 9/14/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> DD opined he would
> prefer INcluding **/*-test.xml , **/*Test.xml , or
> some other known pattern to excluding support files.
> My rationale is that I expect the majority of files
> under src/test
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Sep 2006, Matt Benson
> <[EMAIL PROTECTED]> wrote:
> integrate antunit tests into Ant core until
> after
> > 1.7's release, or can we go ahead and start
> > adding/migrating au tests?
>
> 1.7beta would be enough for me, but we'd also need
On Tue, 5 Sep 2006, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> Although I'm curious to know how this chicken-and-egg thing is
> resolved in Gump.
We build a minimal Ant without running the tests, then we build JUnit
with that version of Ant, then we build Ant again. To make things
more diff
On Tue, 5 Sep 2006, Matt Benson <[EMAIL PROTECTED]> wrote:
> Antunit depends on HEAD. So theoretically antunit
> can't be used in the wild until 1.7 is released (let's
> assume "in the wild" means released components only).
> Do we want to play by these rules ourselves and wait
> to integrate ant
Original-Nachricht
Datum: Tue, 5 Sep 2006 13:44:52 -0500
Von: "Dominique Devienne" <[EMAIL PROTECTED]>
An: "Ant Developers List"
Betreff: Re: antunit integration
Hello Dominique,
> Although I'm curious to know how this chicken-and-egg thing i
> But I'm more worried about the bootstrapping issue,
This chicken-and-egg issue was discussed before; I am
unfortunately too lazy to go find it in the archives,
but the answer was that Ant does not bootstrap antunit
to run its own tests; rather a built antunit is used
with Ant in pretty much the
--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> > xmlns:au="antlib:org.apache.ant.antunit">
> > > includes="**/*.xml"
> > excludes="**/*-support.xml" />
> > <...listener... />
> >
> >
> > I excluded *-support.xml because I thought there
> might
> > be a need for support
<...listener... />
I excluded *-support.xml because I thought there might
be a need for support xml files (hopefully that was
obvious), and I selected a straightforward convention.
What modifications to this strategy do others
advocate?
I've always used **/test/*Test.class for JUnit tests (b
Antunit depends on HEAD. So theoretically antunit
can't be used in the wild until 1.7 is released (let's
assume "in the wild" means released components only).
Do we want to play by these rules ourselves and wait
to integrate antunit tests into Ant core until after
1.7's release, or can we go ahea
12 matches
Mail list logo
