junitdoclet-users Mailing List for JUnitDoclet (Page 2)
Brought to you by:
sgemkow
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(7) |
Feb
(2) |
Mar
(2) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Matt R. <ma...@ra...> - 2002-12-11 00:36:23
|
I'm curious to know if there are any plans to support Cactus testcases or StrutsTest cases in the future. My LoginServletTest extends ServletTestCase and I get the following warning then running junitdoclet: [javadoc] javadoc: warning - TestCase org.apache.webapp.actions.LoginServletTest is invalid. It's not overwritten. Just curious - not a big deal at all. Matt |
From: Matt R. <ma...@ra...> - 2002-12-10 22:22:54
|
I have no specific reason for wanting 3.8.1 - I just saw a message yesterday (can't seem to find it now) that some syntax had changed in 3.8.1 and tests were easier to write now. Just wondering so I could answer this question if it ever does come up. I'm writing a sample app that demonstrates using Xdoclet, Struts, JUnitDoclet, Cactus and other tools to build a webapp and test it. Matt > -----Original Message----- > From: jun...@li... > [mailto:jun...@li...] On > Behalf Of ste...@ob... > Sent: Tuesday, December 10, 2002 3:13 PM > To: jun...@li... > Subject: [Junitdoclet-users] Re: JUnit 3.8.1 > > > Matt asked a question, I'd like to answer: > > > Are the any plans to support Junit 3.8.1 style syntax soon? > Well, it does already. What do you mean? > > I assume (this is just guessing) you have trouble with some > accessor test for a double (or float) value. The third > parameter of assertEquals(double expected, double actual, > double delta) > (the delta) is not there. Right? > > This is not a bug, it's a feature. Let me explain: > > What delta would fit every need? (We would like to use it. > ;-)) Why did Kent and Erich came up with that third parameter anyway? > > -> Because only YOU know, what is appropriate. > > Don't trust a tool that is thinking for you. JUnitDoclet does > not think, so you don't need to outsmart it. JUnitDoclet is > behaving in a predictable way, so whenever you should decide, the > compiler will point you to the place begging for your > decision. Because that is in between markers, JUnitDoclet > does remember > your decision, it won't ask for the same thing twice. > > Again, this answer is just based on a wild guess. > Matt, if this is not your problem, please be more specific > about the syntax of JUnit 3.8.1 you want to use. > > BTW: Thanks for pointing me to the error in the FAQ regarding > "-source 1.4" vs. "-source=1.4". I've fixed it. > > Regards, > > Steffen Gemkow > -- > ObjectFab GmbH > ste...@ob... > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing > Channel http://hpc.devchannel.org/ > _______________________________________________ > Junitdoclet-users mailing list Jun...@li... > https://lists.sourceforge.net/lists/listinfo/junitdoclet-users > |
From: <ste...@ob...> - 2002-12-10 22:10:33
|
Matt asked a question, I'd like to answer: > Are the any plans to support Junit 3.8.1 style syntax soon? Well, it does already. What do you mean? I assume (this is just guessing) you have trouble with some accessor test for a double (or float) value. The third parameter of assertEquals(double expected, double actual, double delta) (the delta) is not there. Right? This is not a bug, it's a feature. Let me explain: What delta would fit every need? (We would like to use it. ;-)) Why did Kent and Erich came up with that third parameter anyway? -> Because only YOU know, what is appropriate. Don't trust a tool that is thinking for you. JUnitDoclet does not think, so you don't need to outsmart it. JUnitDoclet is behaving in a predictable way, so whenever you should decide, the compiler will point you to the place begging for your decision. Because that is in between markers, JUnitDoclet does remember your decision, it won't ask for the same thing twice. Again, this answer is just based on a wild guess. Matt, if this is not your problem, please be more specific about the syntax of JUnit 3.8.1 you want to use. BTW: Thanks for pointing me to the error in the FAQ regarding "-source 1.4" vs. "-source=1.4". I've fixed it. Regards, Steffen Gemkow -- ObjectFab GmbH ste...@ob... |
From: Matt R. <ma...@ra...> - 2002-12-10 04:52:49
|
Are the any plans to support Junit 3.8.1 style syntax soon? Thanks, Matt |
From: Matt R. <ma...@ra...> - 2002-12-10 04:46:57
|
I got this fixed by using the docletpathref attribute to point to a classpath with junitdoclet.jar in it. I also found that using docletpath to point to the junitdoclet.jar file works as well. There doesn't seem to be a need to put junitdoclet.jar into $ANT_HOME/lib. Now I'm getting an error on -source='1.4' - I tried it with and without the quotes, and I get: javadoc: invalid flag: -source=1.4 I tool the equals out so my additionalparam attribute looks like this: additionalparam = "-d test/${module} -buildall -source 1.4"> And it seems to work fine - is this the correct syntax? Thanks, Matt > -----Original Message----- > From: Matt Raible [mailto:ma...@ra...] > Sent: Monday, December 09, 2002 4:29 PM > To: 'jun...@li...' > Subject: Problems running JUnitDoclet as Ant task > > I'm trying to run JUnitDoclet as an Ant task and it can't > seem to find it in my classpath. I've tried referencing it > in my classpath, as well as placing it in $ANT_HOME/lib, but > no luck. Any ideas? Here's my task: > > <target name="junitdoclet" depends="compile-web"> > > <javadoc > packagenames = "org.*" > sourcepath = "src/web" > defaultexcludes = "yes" > doclet = "com.objectfab.tools.junitdoclet.JUnitDoclet" > additionalparam = "-d test/web -buildall -source='1.4'"> > > <classpath refid = "web.test.classpath" /> > > </javadoc> > </target> > > > When it runs, it says: > > junitdoclet: > [javadoc] Generating Javadoc > [javadoc] Javadoc execution > [javadoc] javadoc: Cannot find doclet class > com.objectfab.tools.junitdoclet.JUnitDoclet > [javadoc] 1 error > > So I added this to my task, and it always comes up: > > <available property="junitdoclet.jar.present" > classname="com.objectfab.tools.junitdoclet.JUnitDoclet"/> > <fail unless="junitdoclet.jar.present"> > You must place JUnitDoclet.jar in ${env.ANT_HOME}/lib. > This file is located at ${junitdoclet.jar}. > </fail> > > Thanks, > > Matt > > P.S. I'm using 1.0.2 on Windows XP, JDK 1.4.1, Ant 1.5.1 and Cygwin. > > > > > |
From: Matt R. <ma...@ra...> - 2002-12-09 23:35:48
|
I'm trying to run JUnitDoclet as an Ant task and it can't seem to find it in my classpath. I've tried referencing it in my classpath, as well as placing it in $ANT_HOME/lib, but no luck. Any ideas? Here's my task: <target name="junitdoclet" depends="compile-web"> <javadoc packagenames = "org.*" sourcepath = "src/web" defaultexcludes = "yes" doclet = "com.objectfab.tools.junitdoclet.JUnitDoclet" additionalparam = "-d test/web -buildall -source='1.4'"> <classpath refid = "web.test.classpath" /> </javadoc> </target> When it runs, it says: junitdoclet: [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] javadoc: Cannot find doclet class com.objectfab.tools.junitdoclet.JUnitDoclet [javadoc] 1 error So I added this to my task, and it always comes up: <available property="junitdoclet.jar.present" classname="com.objectfab.tools.junitdoclet.JUnitDoclet"/> <fail unless="junitdoclet.jar.present"> You must place JUnitDoclet.jar in ${env.ANT_HOME}/lib. This file is located at ${junitdoclet.jar}. </fail> Thanks, Matt P.S. I'm using 1.0.2 on Windows XP, JDK 1.4.1, Ant 1.5.1 and Cygwin. |
From: <ste...@ob...> - 2002-11-30 00:09:36
|
Hi everyone, we've just released JUnitDoclet 1.0.2. It's all about bugfixes. Upgrading is recommended. Regards, Steffen Gemkow -- ObjectFab GmbH ste...@ob... |
From: <ste...@ob...> - 2002-10-31 17:01:40
|
Hi, you subscribed to an Email list related to JUnitDoclet. So I want to let you know, version 1.0.1 is out. We'd spent some time to come up with examples how to integrate JUnitDoclet in popular IDEs like IDEA and Eclipse. Enjoy. Regards, Steffen Gemkow -- ObjectFab GmbH ste...@ob... |