You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by Vincent Massol <vm...@pivolis.com> on 2003/05/23 13:24:13 UTC
Missing feature in new Ant integration
Hi Chris,
I'm currently porting the Cactus Maven plugin to use the new Cactus/Ant
integration. However, I have one issue... In the previous version of the
Ant integration there was the possibility of choosing 2 test runners:
text one or swingui one. Currently, only the text runner is supported...
We have several solutions:
1/ add a <runner> tag in the <cactus> task
2/ create a new <cactus-swing> task
What do you think?
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: Missing feature in new Ant integration
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: news [mailto:news@main.gmane.org] On Behalf Of Christopher Lenz
> Sent: 23 May 2003 14:02
> To: cactus-dev@jakarta.apache.org
> Subject: Re: Missing feature in new Ant integration
>
> Hi Vincent,
>
> I must say that I personally see absolutely no point in using a
non-Ant
> test-runner from Ant. Ant is for automated builds, although you can of
> course use it as a fancy launcher for GUI-apps too. Anyway, I'm -1 on
> adding
> that to the <cactus> task, because that task is intimately tied to the
Ant
> test-runner (on purpose).
>
> I'd also not like to add another task for every possible JUnit runner
(why
> stop at the Swing runner? What if I want to use my own fictive
SWT-base
> runner?).
>
> However, one way to support this would be using the good'ole
> <runservertests> task. We could rather easily add support for nested
> <containerset>/containers so that the container start/stop logic could
be
> reused. Then you could specify exactly *how* the tests are run in your
own
> test target.
>
> What do you think?
+1
Having a generic runservertests that does everything except running the
tests (or whatever the user wish to do after the container is started)
would be great.
What about deployment? Would that be left to the user to do or is it
part of the <container> feature?
Thanks
-Vincent
>
> -chris
>
> [PS: still waiting for your feedback on the BC issues ;-) ]
>
> Vincent Massol wrote:
> > Hi Chris,
> >
> > I'm currently porting the Cactus Maven plugin to use the new
Cactus/Ant
> > integration. However, I have one issue... In the previous version of
the
> > Ant integration there was the possibility of choosing 2 test
runners:
> > text one or swingui one. Currently, only the text runner is
supported...
> >
> > We have several solutions:
> >
> > 1/ add a <runner> tag in the <cactus> task
> > 2/ create a new <cactus-swing> task
> >
> > What do you think?
> > Thanks
> > -Vincent
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Missing feature in new Ant integration
Posted by Christopher Lenz <cm...@gmx.de>.
Hi Vincent,
I must say that I personally see absolutely no point in using a non-Ant
test-runner from Ant. Ant is for automated builds, although you can of
course use it as a fancy launcher for GUI-apps too. Anyway, I'm -1 on adding
that to the <cactus> task, because that task is intimately tied to the Ant
test-runner (on purpose).
I'd also not like to add another task for every possible JUnit runner (why
stop at the Swing runner? What if I want to use my own fictive SWT-base
runner?).
However, one way to support this would be using the good'ole
<runservertests> task. We could rather easily add support for nested
<containerset>/containers so that the container start/stop logic could be
reused. Then you could specify exactly *how* the tests are run in your own
test target.
What do you think?
-chris
[PS: still waiting for your feedback on the BC issues ;-) ]
Vincent Massol wrote:
> Hi Chris,
>
> I'm currently porting the Cactus Maven plugin to use the new Cactus/Ant
> integration. However, I have one issue... In the previous version of the
> Ant integration there was the possibility of choosing 2 test runners:
> text one or swingui one. Currently, only the text runner is supported...
>
> We have several solutions:
>
> 1/ add a <runner> tag in the <cactus> task
> 2/ create a new <cactus-swing> task
>
> What do you think?
> Thanks
> -Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org