Re: Running junit tests fails
J.Pietschmann wrote: Peter: I think it points to the fact that we will have to provide a custom ant build, optional.jar and library dependencies, including junit.jar. That's not necessary if people install a proper binary ant distro. It's somewhat like the FOP binary distro: we provide a pre-built jar offering Jimi, JAI and crypto support, something which people building FOP from source not necessarily get. Just had a look at the Ant binary optional.jar. It's got everything but the kitchen sink, including the junit stuff. Would Maven cover the Jimi/JAI/Crypto stuff for us? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
Peter B. West wrote: Just had a look at the Ant binary optional.jar. It's got everything but the kitchen sink, including the junit stuff. That's what I said: they compile in everything officially supported. That's why we run with a customized ant.jar for some time. Would Maven cover the Jimi/JAI/Crypto stuff for us? I have no idea. We might get the LotBC stuff into the Maven repo, but downloading Jimi requires accepting a license, and JAI requires downloading a platform specific distro and running a native installer with all kind of whistles an bells (in particular, possibly requiring root/Admin rights). We can, of course, resort do manual download+install and simply check presence. This should work well with JAI. Jimi is ... more complicated, because it's just a jar, which wont fit the Maven repository. Maybe the old default location of fop-base-dir/lib is still the best. For detecting Jimi/JAI/whatever, we have to supply some sort of Maven plugin, perhaps a Jelly script. Anybody out there with enough time at hand and willing to dive deeper into this? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
On Fri, Dec 12, 2003 at 03:32:35PM +0100, Jeremias Maerki wrote: Nope. With the Ant installation (binary, I've never had to build Ant myself, yet) you get a fully operational optional.jar with has a usable JUnit task as soon as you have junit.jar in %ANT_HOME%/lib. Building FOP (HEAD) without embedded Ant goes like this: - Install Ant binary distribution - set the ANT_HOME environment variable - extend you PATH variable with %ANT_HOME%\bin - Download JUnit and put the junit-version.jar into %ANT_HOME%\lib (if you want to run the testcases) - Download FOP from CVS - go to the xml-fop directory and run ant or ./ant.sh I did that and it works fine. Until now I have been confused about ant. That may have been caused by the embedded ant jar files in many projects, and their possible incompatibility. That makes that you rely on their build script, and do not think about it. I every project requires one to obtain and install a reasonably recent ant, and avoids incompatibilities with that, a developer quickly gets up to speed with it. Similarly with adding junit or other supporting packages. Building C projects seems easy: ./configure, make, make_install. But that is only the case if the whole tool chain is present in the system. The same here. Having to have ant and junit seems a reasonable requirement, provided no project requires one to have their own ever so slightly tweaked embedded version. Regards, Simon -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
Nope. With the Ant installation (binary, I've never had to build Ant myself, yet) you get a fully operational optional.jar with has a usable JUnit task as soon as you have junit.jar in %ANT_HOME%/lib. Building FOP (HEAD) without embedded Ant goes like this: - Install Ant binary distribution - set the ANT_HOME environment variable - extend you PATH variable with %ANT_HOME%\bin - Download JUnit and put the junit-version.jar into %ANT_HOME%\lib (if you want to run the testcases) - Download FOP from CVS - go to the xml-fop directory and run ant or ./ant.sh On 12.12.2003 02:42:17 Peter B. West wrote: I seem to recall that one has to build ant for the particular set of optional facilities that one wants. Does this ring a bell for anyone? From the manual: Make sure you have downloaded any auxiliary jars required to build tasks you are interested in. These should either be available on the CLASSPATH or added to the lib directory. See Library Dependencies for a list of jar requirements for various features. Note that this will make the auxiliary jars available for the building of Ant only. For running Ant you will still need to make the jars available as described under Installing Ant. / These seem to be in addition to optional.jar. I think it points to the fact that we will have to provide a custom ant build, optional.jar and library dependencies, including junit.jar. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
Jeremias Maerki wrote: Nope. With the Ant installation (binary, I've never had to build Ant myself, yet) you get a fully operational optional.jar with has a usable JUnit task as soon as you have junit.jar in %ANT_HOME%/lib. The ant jar in the FOP CVS was a bit customized: Keiron moved the xslt task into ant.jar and omitted optional.jar completely. I vaguely remember someone upgradesd the ant jars somewhere (HEAD or maintenance, don't recall). In any case, somebody stuck with an earlier FOP checkout might have problems... Building FOP (HEAD) without embedded Ant goes like this: ... - extend you PATH variable with %ANT_HOME%\bin or copy/move the ant scripts into a directory which is already in the path. There is, however, the inconvenience called FOP task somewhere, which needs to refer to ant jars for compilation. I believe we need to fumble a bit with build.xml in order to get ant.jar into the classpath for this. I even believe the java file is currently unconditionally compiled, which seems unprudent. Peter: I think it points to the fact that we will have to provide a custom ant build, optional.jar and library dependencies, including junit.jar. That's not necessary if people install a proper binary ant distro. It's somewhat like the FOP binary distro: we provide a pre-built jar offering Jimi, JAI and crypto support, something which people building FOP from source not necessarily get. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
Simon Pepping wrote: When I try to run the junit tests on the code checked out from CVS HEAD, I get a failure because ant cannot create task or type of type: junit. I do not know anything about junit. I had hoped this target would run out of the box. snip/ BUILD FAILED file:/fsd/source/xml-fop/build.xml:659: Could not create task or type of type: junit. Ant could not find the task or a class this task relies upon. junit is version 3.8.1. I get the same thing, but I also dont know how to solve it. Looking in the build.xml doesnt reveal any *obvious* dependencies for junit that are missing. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
BUILD FAILED file:/fsd/source/xml-fop/build.xml:659: Could not create task or type of type: junit. Ant could not find the task or a class this task relies upon. junit is version 3.8.1. I get the same thing, but I also dont know how to solve it. Looking in the build.xml doesnt reveal any *obvious* dependencies for junit that are missing. You may want to add the jar containing the junit task in the JUNIT_HOME/lib directory. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stan Pinte. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
Stan Pinte wrote: You may want to add the jar containing the junit task in the JUNIT_HOME/lib directory. Whats the name of the jar containing the junit ant task definition then? Ive added the junit.jar, there is also a test.jar and a src.jar in my junit directory (no lib sub dir though!) The junit.present condition in the build.xml file doesnt let you procced without the junit.jar. However, I'm not sure if junit.jar contains the ant task definition. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
On Wed, 10 Dec 2003 11:44:08 +, Chris Bowditch [EMAIL PROTECTED] wrote: Stan Pinte wrote: You may want to add the jar containing the junit task in the JUNIT_HOME/lib directory. Whats the name of the jar containing the junit ant task definition then? Ive added the junit.jar, there is also a test.jar and a src.jar in my junit directory (no lib sub dir though!) The junit.present condition in the build.xml file doesnt let you procced without the junit.jar. However, I'm not sure if junit.jar contains the ant task definition. I don't know, you may want to submit that to the junit list. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stan Pinte. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
junit.jar is sufficient. The jar should be placed in %ANT_HOME%/lib. Use JUnit 3.8.1 or later to be sure. The JUnit task is included in Ant's optional.jar but only works if junit.jar is present in %ANT_HOME%/lib. Actually, I don't understand why the JUnit suport is recognized but the test cases don't work. On 10.12.2003 12:44:08 Chris Bowditch wrote: Whats the name of the jar containing the junit ant task definition then? Ive added the junit.jar, there is also a test.jar and a src.jar in my junit directory (no lib sub dir though!) The junit.present condition in the build.xml file doesnt let you procced without the junit.jar. However, I'm not sure if junit.jar contains the ant task definition. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
On Wed, 10 Dec 2003 14:28:23 +0100, Jeremias Maerki [EMAIL PROTECTED] wrote: junit.jar is sufficient. The jar should be placed in %ANT_HOME%/lib. sorry for my mistake... Use JUnit 3.8.1 or later to be sure. The JUnit task is included in Ant's optional.jar but only works if junit.jar is present in %ANT_HOME%/lib. Actually, I don't understand why the JUnit suport is recognized but the test cases don't work. On 10.12.2003 12:44:08 Chris Bowditch wrote: Whats the name of the jar containing the junit ant task definition then? Ive added the junit.jar, there is also a test.jar and a src.jar in my junit directory (no lib sub dir though!) The junit.present condition in the build.xml file doesnt let you procced without the junit.jar. However, I'm not sure if junit.jar contains the ant task definition. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stan Pinte. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
On Wed, Dec 10, 2003 at 02:28:23PM +0100, Jeremias Maerki wrote: junit.jar is sufficient. The jar should be placed in %ANT_HOME%/lib. Use JUnit 3.8.1 or later to be sure. The JUnit task is included in Ant's optional.jar but only works if junit.jar is present in %ANT_HOME%/lib. Actually, I don't understand why the JUnit suport is recognized but the test cases don't work. junit-3.8.1.jar is the lib subdirectory of the checked out distribution. The build script declares this directory to be ANT_HOME. When I put the junit jar file there, the JUnit support was recognized. The build script does not add the junit jar file to the LOCALCLASSPATH. But when I did that it made no difference. Ant's failure message mentions optional.jar. I do not have that because it does not come with the checkout. Could that be the cause? I run Sun's java version 1.4.2_01 on linux. On 10.12.2003 12:44:08 Chris Bowditch wrote: Whats the name of the jar containing the junit ant task definition then? Ive added the junit.jar, there is also a test.jar and a src.jar in my junit directory (no lib sub dir though!) The junit.present condition in the build.xml file doesnt let you procced without the junit.jar. However, I'm not sure if junit.jar contains the ant task definition. Jeremias Maerki Regards, Simon -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit tests fails
Looks like it. Please download the latest Ant release and install it following Ant's installation instructions. Then use ant.bat/ant.sh to build FOP and not build.bat. Ant can be found at http://ant.apache.org. I've heard that best practice is not to bundle Ant with a project but to make an Ant installation a requirement on every machine someone wants to build Java projects on. Looks like we hit one of the reasons for this best practice here. I'll raise that point on fop-dev. Sorry for the trouble caused. I was the one to introduce JUnit tests in the build.xml for HEAD. On 10.12.2003 20:46:52 Simon Pepping wrote: Ant's failure message mentions optional.jar. I do not have that because it does not come with the checkout. Could that be the cause? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Running junit tests fails
When I try to run the junit tests on the code checked out from CVS HEAD, I get a failure because ant cannot create task or type of type: junit. I do not know anything about junit. I had hoped this target would run out of the box. What should I do to make it work? ./build.sh package javadocs junit ... init-avail: [echo] Apache Ant version 1.5.1 compiled on October 2 2002 [echo] Jimi Support NOT Present [echo] JAI Support NOT Present [echo] JCE Support PRESENT [echo] JUnit Support PRESENT ... init: [echo] --- Fop 1.0dev [1999-2003] [echo] See build.properties and build-local.properties for additional build settings ... junit: [echo] Running basic functionality tests for fop-transcoder.jar BUILD FAILED file:/fsd/source/xml-fop/build.xml:659: Could not create task or type of type: junit. Ant could not find the task or a class this task relies upon. junit is version 3.8.1. -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]