Zarro boogs found

[Assaf Arkin]

Everything that was filed against Buildr is either fixed, not reproducible
(a couple of issues were broken repositories), or not in scope for 1.3.
 With that in mind, let's make a 1.3 release.

I'll start:
+1

Assaf

[Tal Rotbart]

Yay!

On Tue, Apr 22, 2008 at 11:13 AM, Assaf Arkin <arkin@...> wrote:
> Everything that was filed against Buildr is either fixed, not reproducible
>  (a couple of issues were broken repositories), or not in scope for 1.3.
>   With that in mind, let's make a 1.3 release.
>
>  I'll start:
>  +1
>
>  Assaf
>

[Alexis Midon]

youuhhhh go go go

On Mon, Apr 21, 2008 at 6:16 PM, Tal Rotbart <redbeard@...> wrote:

> Yay!
>
> On Tue, Apr 22, 2008 at 11:13 AM, Assaf Arkin <arkin@...> wrote:
> > Everything that was filed against Buildr is either fixed, not
> reproducible
> >  (a couple of issues were broken repositories), or not in scope for 1.3.
> >   With that in mind, let's make a 1.3 release.
> >
> >  I'll start:
> >  +1
> >
> >  Assaf
> >
>

[Matthieu Riou-5]

On Mon, Apr 21, 2008 at 6:13 PM, Assaf Arkin <arkin@...> wrote:

> Everything that was filed against Buildr is either fixed, not reproducible
> (a couple of issues were broken repositories), or not in scope for 1.3.
>  With that in mind, let's make a 1.3 release.
>
> I'll start:
> +1
>

Yep. A big +1 from me.


>
> Assaf
>

[Victor Hugo Borja]

We'll have release party!  +1

On Mon, Apr 21, 2008 at 8:13 PM, Assaf Arkin <arkin@...> wrote:

> Everything that was filed against Buildr is either fixed, not reproducible
> (a couple of issues were broken repositories), or not in scope for 1.3.
>  With that in mind, let's make a 1.3 release.
>
> I'll start:
> +1
>
> Assaf
>



--
vic

Quaerendo invenietis.

[Timo Rantalaiho]

Hello,

It would be great to get this fixed before the release:

  https://issues.apache.org/jira/browse/BUILDR-62

Sorry for the late report!

Best wishes,
Timo
A beginning Buildr user

--
Timo Rantalaiho          
Reaktor Innovations Oy    <URL: http://www.ri.fi/ >

[Assaf Arkin]

On Mon, Apr 21, 2008 at 9:29 PM, Timo Rantalaiho <Timo.Rantalaiho@...>
wrote:

> Hello,
>
> It would be great to get this fixed before the release:
>
>  https://issues.apache.org/jira/browse/BUILDR-62
>
> Sorry for the late report!


You're right about RunWith, I'm fixing that.

In 1.3 you can still filter test cases by class/package name, and that's
handled uniformly across all test frameworks using test.include/exclude.

What you can't do is convince JUnit to select classes that are not JUnit
test cases, which was possible in 1.2, and a convenient hack before we had a
good test framework API.

In 1.3 we cleaned that up.  We now have an API for adding new test
framework, with some convenience methods for the Java frameworks, and even
three BDD frameworks using it (check out buildr/java/bdd_frameworks.rb).

So that was a conscious decision to break the old behavior but move
developer to the new API.

(Note: we still need to work on a uniform reporting mechanism for all the
different test frameworks)

Assaf

>
>
> Best wishes,
> Timo
> A beginning Buildr user
>
> --
> Timo Rantalaiho
> Reaktor Innovations Oy    <URL: http://www.ri.fi/ >
>

[Timo Rantalaiho]

On Mon, 21 Apr 2008, Assaf Arkin wrote:

> In 1.3 you can still filter test cases by class/package name, and that's
> handled uniformly across all test frameworks using test.include/exclude.
>
> What you can't do is convince JUnit to select classes that are not JUnit
> test cases, which was possible in 1.2, and a convenient hack before we had a
> good test framework API.
>
> In 1.3 we cleaned that up.  We now have an API for adding new test
> framework, with some convenience methods for the Java frameworks, and even
> three BDD frameworks using it (check out buildr/java/bdd_frameworks.rb).
>
> So that was a conscious decision to break the old behavior but move
> developer to the new API.
>
> (Note: we still need to work on a uniform reporting mechanism for all the
> different test frameworks)

Thanks Assaf! It seems that with the include / exclude +
@RunWith fix, we can continue with the "convenient hack" of
using the JUnit runner for running JDave specs. I had no idea
that include and exclude were so easy to use, and hope to try
them soon in practice.

Best wishes,
Timo

--
Timo Rantalaiho          
Reaktor Innovations Oy    <URL: http://www.ri.fi/ >

[Assaf Arkin]

On Wed, Apr 23, 2008 at 1:24 PM, Timo Rantalaiho <Timo.Rantalaiho@...>
wrote:

> On Mon, 21 Apr 2008, Assaf Arkin wrote:
> > In 1.3 you can still filter test cases by class/package name, and that's
> > handled uniformly across all test frameworks using test.include/exclude.
> >
> > What you can't do is convince JUnit to select classes that are not JUnit
> > test cases, which was possible in 1.2, and a convenient hack before we
> had a
> > good test framework API.
> >
> > In 1.3 we cleaned that up.  We now have an API for adding new test
> > framework, with some convenience methods for the Java frameworks, and
> even
> > three BDD frameworks using it (check out buildr/java/bdd_frameworks.rb).
> >
> > So that was a conscious decision to break the old behavior but move
> > developer to the new API.
> >
> > (Note: we still need to work on a uniform reporting mechanism for all the
> > different test frameworks)
>
> Thanks Assaf! It seems that with the include / exclude +
> @RunWith fix, we can continue with the "convenient hack" of
> using the JUnit runner for running JDave specs. I had no idea
> that include and exclude were so easy to use, and hope to try
> them soon in practice.

Thanks.  Can we close this issue?  The release will include the @RunWith
fix.

Assaf


>
>
> Best wishes,
> Timo
>
> --
> Timo Rantalaiho
> Reaktor Innovations Oy    <URL: http://www.ri.fi/ >
>

[Timo Rantalaiho]

On Wed, 23 Apr 2008, Assaf Arkin wrote:
> Thanks.  Can we close this issue?  The release will include the @RunWith
> fix.

Yep! I updated from trunk, tested briefly and closed the
issue (with fix version 1.3).

Best wishes,
Timo

--
Timo Rantalaiho          
Reaktor Innovations Oy    <URL: http://www.ri.fi/ >

[Alex Boisvert-3]

+1

the most awaited release of buildr so far :)


On Mon, Apr 21, 2008 at 6:13 PM, Assaf Arkin <arkin@...> wrote:

> Everything that was filed against Buildr is either fixed, not reproducible
> (a couple of issues were broken repositories), or not in scope for 1.3.
>  With that in mind, let's make a 1.3 release.
>
> I'll start:
> +1
>
> Assaf
>