On Wed, 15 Dec 2004, Yves Martin <[EMAIL PROTECTED]> wrote:
> But why not create a junit2 and made junit deprecated ?
Because you'll have to convince us as well as the existing
task user base why they'd prefer . Less options and
potentially more tasks won't be good selling arguments ;-)
> Wa
Stefan Bodewig <[EMAIL PROTECTED]> writes:
> Before you get too excited by the opportunities (and yes, has
> collected quite a bit of historic cruft) - we are not going to remove a
> single attribute or nested element of any existing task, since backwards
> compatibility is an extremely important
On Wed, 15 Dec 2004, Yves Martin <[EMAIL PROTECTED]> wrote:
> As a proposal, I think a simpler 'junit' task would be enough and
> may avoid troubles:
Before you get too excited by the opportunities (and yes, has
collected quite a bit of historic cruft) - we are not going to remove
a single att
Hello,
I'm working on a build system based on plugin, and I'm currently writting a
'junit' plugin to call test cases and to generate report...
And I find the 'junit' optionnal task really complex (from the user-side point
of view). The big trouble for me is that it is possible to declare
