Sorry for sending the wrong message then.

Jen-Philippe, if you can reproduce the problem in an environment on which we
can work (or even better write a spec), I'd be happy to fix the problem.

Thanks,

Antoine

On Tue, Mar 23, 2010 at 11:31, lacton <[email protected]> wrote:

> There's even a spec for this behavior. :-)
>
> <code>
>  describe 'when there was a successful test run already' do
>
>    it 'should not run tests if nothing changed' do
>      lambda { test_task.invoke }.should_not run_task('foo:test')
>    end
> </code>
>
> lacton
>
> On Tue, Mar 23, 2010 at 4:33 PM, Alex Boisvert <[email protected]>
> wrote:
> > Just want to confirm what Rhett said, the tests shouldn't be run twice if
> > you run "buildr package" twice without changing anything.
> >
> > alex
> >
> >
> > On Tue, Mar 23, 2010 at 8:25 AM, Jean-Philippe Caruana <
> > [email protected]> wrote:
> >
> >> Le 23/03/2010 16:19, Rhett Sutphin a écrit :
> >>
> >>> Hi Jean-Phillipe,
> >>>
> >>
> >> Hi Rhett,
> >>
> >>  I don't understand how buildr works - I thought i did though.
> >>>> every time i launch "buildr package" in artifactToBuild or "buildr
> >>>> test", it launches all the tests in commons-test and commons-util even
> >>>> if nothing changed in this projects. These can be pretty long. How can
> >>>> I do to change this behaviour ?
> >>>>
> >>>
> >>> It does this if you just run `buildr package` twice, back-to-back, with
> >>> no changes to anything anywhere? That should not be.
> >>>
> >>
> >> that's what I thought too and that's my question.
> >>
> >>
> >>  If you run with
> >>> --trace, buildr will show you (in great detail) which tasks it is
> >>> deciding to run and why. Try that and see what you find.
> >>> Dependency issues like this can sometimes be hard to track down. I'd
> >>> suggest starting with commons-test and seeing if you can get `buildr
> >>> package` to work properly, then move to the next project in the chain,
> >>> etc.
> >>>
> >>
> >> okay, it was my next step, but I was a little lazy since '--trace' is
> >> really verbose. I will try to find out something in there.
> >>
> >>
> >> ps : sorry for the end of mail crap in french/english : it's
> automatically
> >> added by my company's smtp server and I can't remove it.
> >>
> >>
> >> -- Jean-Philippe Caruana
>

Reply via email to