Hi all! >> I believe we are talking in context of Debian. Since we were talking >> about the installation of junit4 and ant in Debian. >> And the 1st solution I provided (which you quoted here) can apply to >> any package maintainer. > > Exactly. All the world's a Debian package. Except I'm just a user in > this > context, and a relatively clueless one, at that. > >> Overriding ant properties is a generic thing, >> nothing specific to Debian. > > Quite true, but debhelper and cdbs are.
I think there is some misunderstanding here :) Onkar suggests some structure like this in *your* project : * build.xml : use ${lib.dir}/junit.jar * build.properties : define lib.dir=lib/ * lib/junit.jar : your own JUnit jar (with all that your project will be portable accros distro and OS) Given that, Onkar said that, if some DD wants to package *your* project, it will either : #1 use an override to set "lib.dir=/usr/share/java/" #2 use a tool like CDBS to set ant classpath via DEB_JARS But maybe you're working on an internal/non-free-software project and have no need for Debian packaging :) FYI, Ant upstream authors recommends [1] to use <classpath> attribute for <junit> task instead of relying on Ant Classpath. So, to conclude on this : - You may use an explicit junit.jar (using properties or classpath as your prefer) - I'll not restore this link to /usr/share/ant/lib/ - I'll add a NEWS.Debian about this in next upload [1] http://ant.apache.org/manual/install.html#optionalTasks Kinds regards, -- Damien Raude-Morvan / www.drazzib.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org