Leo Simons wrote:
ouch!
this slipped through I guess because just about everyone has a junit
lib inside their $ANT_HOME/lib. Which will probably fix things :D
Release has already been made and voted upon though, so can't change
that. No biggy I think. Feel free to patch cvs so it works in the next
point release.
logkit and framework have different styles for how they manage
dependencies. can i switch it to use the framework style? i.e. use the
check-targets.ent and check-targets.properties files. Can i also go
ahead and do this for phoenix (which also needs junit)?
cheers,
- Leo
Huw Roberts wrote:
Hi,
When i download LogKit-1.2 to a fresh directory and do a build it
fails because it can't find junit. It turns out it is looking for:
${tools.dir}/lib/junit-3.7.jar
where by default:
tools.dir = ../avalon/tools
The latest version of framework puts the jar in ../avalon/lib, and
only after running the import-junit ant task. There are also a
number of other files that are looked for in ../avalon/tools. I
don't know if this should hold up a release, but it definitely needs
to be addressed. Before i go any farther, is there something i'm
missing?
- huw
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
