Re: Classpath setup problem
Simon Pepping wrote: What do you mean with repository? xml-fop/lib? No, $HOME/lib. I thought of either adding exclude name=fop*.jar/ exclude name=batik*.jar/ and perhaps a few more to filesets which load from optional.lib.dir, or have specific filesets for Jimi, JAI, JCE providers etc. Neither is completely foolproof, in particular ther may be people with JCE providers other than bouncy castle. J.Pietschmann
Re: Classpath setup problem
On Tue, Sep 06, 2005 at 10:48:11PM +0200, J.Pietschmann wrote: Next question: I used to have old (maintenance branch) jars for FOP and Batik in the repository, which causes compilation problems. Therefore it might be a good idea to include only specific fles rather than *.jar in the classpath set. WDYT? What do you mean with repository? xml-fop/lib? Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Classpath setup problem
J.Pietschmann schrieb: Hi devs, I just upgraded to Ant 1.6.5 and the junit tasks stopped working (see Ant FAQ faq.html#delegating-classloader). I really liked my setup where all jars were in a single directory. :-( Yeah, with the help of those nice build.bat|sh ;-) It's too late in the evening for advanced reshuffling of important libraries. What's your setup? apt-get install ant junit which puts a symlink to junit.jar in /usr/share/ant/lib/ -- Christian
Re: Classpath setup problem
Just upgraded to Ant 1.6.5 on Windoze. 1. Unpack binaries 2. Adjust ANT_HOME env variable (%ANT_HOME%\bin is already in the PATH) 3. Copy junit-3.8.1.jar into the lib directory of the Ant installation. ...works. On 06.09.2005 00:53:13 J.Pietschmann wrote: Hi devs, I just upgraded to Ant 1.6.5 and the junit tasks stopped working (see Ant FAQ faq.html#delegating-classloader). I really liked my setup where all jars were in a single directory. :-( It's too late in the evening for advanced reshuffling of important libraries. What's your setup? J.Pietschmann Jeremias Maerki
Re: Classpath setup problem
Jeremias Maerki wrote: 3. Copy junit-3.8.1.jar into the lib directory of the Ant installation. Yeah, this is exactly what I like to avoid: If I kill the installation, there's a chance all jars put there are gone and have to be extracted from offline archives in the new installation. I'll probably move all jars to ~/.ant/lib and point optional.lib.dir there. Grmbl. J.Pietschmann
Re: Classpath setup problem
Simon Pepping wrote: I used to use a script for ant that adds junit.jar to the classpath. Since Debian Sarge, it works out of the box, as Christian said. Thanks for the encouragement. After another round of getting the long, well meaning and utterly useless Ant messsage about a task not found, this time because Cygwin $HOME is not Java user.home and therefore ~/.ant/lib isn't searched for jars, I finally solved this by adding -lib ~/java/lib to ANT_ARGS, thereby also making the setting of optional.lib.dir in build-local.properties obsolete. My .antrc is now more than 50 lines! Next question: I used to have old (maintenance branch) jars for FOP and Batik in the repository, which causes compilation problems. Therefore it might be a good idea to include only specific fles rather than *.jar in the classpath set. WDYT? J.Pietschmann
Classpath setup problem
Hi devs, I just upgraded to Ant 1.6.5 and the junit tasks stopped working (see Ant FAQ faq.html#delegating-classloader). I really liked my setup where all jars were in a single directory. :-( It's too late in the evening for advanced reshuffling of important libraries. What's your setup? J.Pietschmann
