svn commit: r382315 - /ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTaskMirror.java

Author: kevj Date: Wed Mar 1 23:42:41 2006 New Revision: 382315 URL: http://svn.apache.org/viewcvs?rev=382315&view=rev Log: don't need final in interface Modified: ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTaskMirror.java Modified: ant/core/trunk/src/main/o

Re: Junut4

+1 for a separate task, packaged in an Ant library. This one could be release before Ant 1.7.0 which would give people using JUnit4 more support sooner. Personally I'd even prefer the JUnit team to provide that Ant library so they have to keep up with their API changes themselves 8-) That

Re: Junut4

On Wed, 01 Mar 2006, Jesse Glick <[EMAIL PROTECTED]> wrote: > Not really clear to me at this point whether the significant > features of JUnit 4 can be accommodated comfortably inside > or whether a separate task would be better. +1 for a separate task, packaged in an Ant library. This one coul

Re: xalan2.present test broken

On Wed, 01 Mar 2006, Steve Loughran <[EMAIL PROTECTED]> wrote: > We need a test for a trax engine being around, for things like > junitreport. But this code doesnt work > > classname="org.apache.xalan.transformer.TransformerImpl" >classpathref="classpath"/> > > Not on java1.5

Re: Junut4

On Wed, 01 Mar 2006, Steve Loughran <[EMAIL PROTECTED]> wrote: > Martijn Kruithof wrote: >> Furthermore I thought junit 4 would get rid of the distinction >> between failure and error, wouldn't we want to remain in-line with >> this new junit behaviour when running junit 4 testcases in an junit >>

Re: svn commit: r381780 - in /ant/core/trunk: WHATSNEW docs/manual/OptionalTasks/junit.html src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java src/main/org/apache/tools/ant/t

On Wed, 01 Mar 2006, Jesse Glick <[EMAIL PROTECTED]> wrote: > Stefan Bodewig wrote: >> Will this patch still allow me to run those tests? Or will >> wrapping the tests in a JUnit4TestAdapter force me to use >> annotations? > > No, you can still use the 3-compatible tests as before. Great. > Yo

DO NOT REPLY [Bug 38807] - Add an errorproperty parameter to task, like the junit task's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 38807] - Add an errorproperty parameter to task, like the junit task's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 38811] - Support JUnit 4

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: svn commit: r382055 - /ant/core/trunk/build.xml

[EMAIL PROTECTED] wrote: let's not save XML reports to the project dir, but instead somewhere under build/ and stick the results in a directory parallel to it. URL: http://svn.apache.org/viewcvs/ant/core/trunk/build.xml?rev=382055&r1=382054&r2=382055&view=diff @@ -1596,8 +1600,8 @@ -

svn commit: r382127 - /ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java

Author: jglick Date: Wed Mar 1 11:13:16 2006 New Revision: 382127 URL: http://svn.apache.org/viewcvs?rev=382127&view=rev Log: Tweak: in case junit-3.8.1.jar and junit-4.0.jar are on CP but in that order, and running JDK 1.4-, at least run JUnit 3.x tests. Modified: ant/core/trunk/src/main/o

Re: Junut4 (was Re: svn commit: r381780 - in /ant/core/trunk: WHATSNEW docs/manual/OptionalTasks/junit.html src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java src/main/org/

Steve Loughran wrote: There was some discussion of junit4 implications in the ant-user mail list, Ah, thanks for the pointer, missed that before. Some things I can extract from that thread: - ignored tests ought to be reported (currently they are just silently skipped) - should support s

Re: JUnit4 support - done?

Jon Skeet wrote: So, having just seen the commit and bug 38811 notes for JUnit4 support - does that mean it's all done? Well probably you should try it and judge for yourself whether it's working well enough. :-) The impl is a bit hackish due to the need to keep full JUnit 3 compatibility

Re: svn commit: r381780 - in /ant/core/trunk: WHATSNEW docs/manual/OptionalTasks/junit.html src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java src/main/org/apache/tools/ant

Martijn Kruithof wrote: Isn't this a bit premature, junit 4 isn't even "out" yet. Seems junit.org has not announced it, but it's there for download and semi-announced at http://sourceforge.net/projects/junit. Furthermore I thought junit 4 would get rid of the distinction between failure and

Re: svn commit: r381780 - in /ant/core/trunk: WHATSNEW docs/manual/OptionalTasks/junit.html src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java src/main/org/apache/tools/a

Stefan Bodewig wrote: I haven't looked into the implemenation of JUnit4TestAdapter so I have to ask you 8-) Sure, was expecting some questions here... Even if I have JUnit 4 on my CLASSPATH I can still use JUnit 3 style of tests (no annotations, naming conventions instead). Yes. Will this

Re: xalan2.present test broken

Steve Loughran wrote: We need a test for a trax engine being around, for things like junitreport. But this code doesnt work Not on java1.5, even though xsltc is around. If you're running Java 1.4 or higher there *has* to be an XSLT engine available acc. to the JAXP spec, I think. -J.

svn commit: r382058 - in /ant/core/trunk/src/etc: junit-frames.xsl log.xsl

Author: stevel Date: Wed Mar 1 07:33:07 2006 New Revision: 382058 URL: http://svn.apache.org/viewcvs?rev=382058&view=rev Log: minor layout tweaks to make it slightly more readable, updated year and corrected an old URL Modified: ant/core/trunk/src/etc/junit-frames.xsl ant/core/trunk/src

svn commit: r382055 - /ant/core/trunk/build.xml

Author: stevel Date: Wed Mar 1 07:31:57 2006 New Revision: 382055 URL: http://svn.apache.org/viewcvs?rev=382055&view=rev Log: let's not save XML reports to the project dir, but instead somewhere under build/ and stick the results in a directory parallel to it. Modified: ant/core/trunk/build

svn commit: r382017 - /ant/core/trunk/build.xml

Author: stevel Date: Wed Mar 1 05:49:04 2006 New Revision: 382017 URL: http://svn.apache.org/viewcvs?rev=382017&view=rev Log: and turn off halting on failure until later Modified: ant/core/trunk/build.xml Modified: ant/core/trunk/build.xml URL: http://svn.apache.org/viewcvs/ant/core/trunk/

AW: svn commit: r381934 - /ant/core/trunk/docs/manual/cover.html

>URL: http://svn.apache.org/viewcvs?rev=381934&view=rev >Log: >Fix the "strange" bahaviour reported by Steve Meredith. > >Modified: >ant/core/trunk/docs/manual/cover.html > > Apache Ant 1.7 Manual > This is the manual for version 1.7alpha of >- http://ant.apache.org/index.html";>Apache Ant

svn commit: r382011 - /ant/core/trunk/build.xml

Author: stevel Date: Wed Mar 1 05:27:01 2006 New Revision: 382011 URL: http://svn.apache.org/viewcvs?rev=382011&view=rev Log: tweak how tests run -you get the junit report if a trax impl is present -we fail afterwards if a test failed or errored -commonality of the two junit runs factored out in

xalan2.present test broken

We need a test for a trax engine being around, for things like junitreport. But this code doesnt work Not on java1.5, even though xsltc is around. Who wants to come up with the tests for an xsltc engine being found? Do we want to make this a ? -steve

Junut4 (was Re: svn commit: r381780 - in /ant/core/trunk: WHATSNEW docs/manual/OptionalTasks/junit.html src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java src/main/org/apache/t

Martijn Kruithof wrote: Isn't this a bit premature, junit 4 isn't even "out" yet. shipped last week. Gump is still recovering. Furthermore I thought junit 4 would get rid of the distinction between failure and error, wouldn't we want to remain in-line with this new junit behaviour when runn

svn commit: r381998 - /ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/net/FTP.java

Author: stevel Date: Wed Mar 1 03:59:54 2006 New Revision: 381998 URL: http://svn.apache.org/viewcvs?rev=381998&view=rev Log: include the caught exception when relayed Modified: ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/net/FTP.java Modified: ant/core/trunk/src/main/or

Re: svn commit: r381780 - in /ant/core/trunk: WHATSNEW docs/manual/OptionalTasks/junit.html src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java src/main/org/apache/tools/ant/tas

Isn't this a bit premature, junit 4 isn't even "out" yet. Furthermore I thought junit 4 would get rid of the distinction between failure and error, wouldn't we want to remain in-line with this new junit behaviour when running junit 4 testcases in an junit 4 environment? Martijn --

Re: JUnit4 support - done?

1.7 isn't final yet, all options are still open. Jon Skeet wrote: So, having just seen the commit and bug 38811 notes for JUnit4 support - does that mean it's all done? Should I "call off the hounds" as it were in terms of the JUnit team getting together with the Ant and Maven teams? Or should

JUnit4 support - done?

So, having just seen the commit and bug 38811 notes for JUnit4 support - does that mean it's all done? Should I "call off the hounds" as it were in terms of the JUnit team getting together with the Ant and Maven teams? Or should we still be looking at a transfer of ownership, as it were? Jon Cl