[Junitdoclet-users] Updates for the Eclipse and ant Setup documentation.

[Mike K. <mki...@al...>]

ste...@ob... wrote:
> Actually, we are working on a new version of JUnitDoclet
> which is going to be a _real_ plugin to eclipse (and to other 
> IDEs). We've seen many complaints from people that 
> had problems to get it started as an external tool (both in 
> IDEA and in Eclipse), so the plugin is a logical step.
> The importance of Eclipse has been shifting since the 
> release of JUnitDoclet. I -personally- may prefer IDEA, but 
> many people don't want to spend money if they can get a 
> similar tool for free. Eclipse-plugin is a MUST HAVE now.

Having tried to use junitdoclet in Eclipse, I think some of the problems =
can be improved by documentation changes.  But not all of them.

I'm using Eclipse 2.1.1 under Windows 2000.

I started off by trying to install it as an external tool  Eventually I =
gave up because I couldn't provide an alternate -properties file, and even =
making it work without alternate templates required hacking up the =
provided bat files.   Too much of a maintenance nightmare for very little =
gain.  Some of this could be reduced by rewriting the bat files to take =
arguments in arbitrary order.

However, I'm including a revised Eclipse IDE readme file for Eclipse 2.1.1 =
that will make it a little easier for those who can use it "out of the =
box."

[readme-Eclipse-2.1.1.txt]

Using it as an ant target worked a little better.  There will still =
problems with the example script under Eclipse 2.1.1.

Here's a revised Eclipse ant target to add to the documentation.

This target assumes you have a "compile" target and a "compile.classpath" =
property (seems likely).
This target assumes that you've put the JUnitDoclet.jar and =
packagelister.jar files in ./src/support/JUnitDoclet/
It's assumed that your source code is in ./src, and that your test cases =
will be built in ./test-src.

If you want to specify an alternate template file, add the following to =
additionalparam.   You cannot specify a relative path.

   -properties ABSOLUTE_PATH_TO_YOUR_junitdoclet.properties_FILE


  <target name=3D"junitdoclet" description=3D"Generate test cases" =
depends=3D"compile">
=09<path id=3D"junitdoclet.classpath">
=09=09<path refid=3D"compile.classpath"/>
        <pathelement path =3D"./src/support/JUnitDoclet/JUnitDoclet.jar"/>
        <pathelement path =
=3D"./src/support/JUnitDoclet/packagelister.jar"/>
=09</path>
    <javadoc
      sourcepath      =3D "./src"
      destdir=09=09  =3D "./test-src"
      packagenames    =3D "*"
      defaultexcludes =3D "yes"
      doclet          =3D "com.objectfab.tools.junitdoclet.JUnitDoclet"
      docletpathref   =3D "junitdoclet.classpath"
      additionalparam =3D "-buildall">
      <classpath refid=3D"compile.classpath"/>
    </javadoc>
  </target>