I'm currently looking at the executioncontext branch, and noticed
something in it's api/build.xml.  It makes use of a ${lib.dir} to
include local jars into it's classpath.  The assumption being you
might want to change the value of that.

However, it then hard-codes the lib name when accessing other
components jars.  That seems quite wrong to me.

And, this same pattern is used thru all build.xml.  I'm thinking we
should remove lib.dir, build.dir, etc, and just hard-code them.

ps: this really has nothing to do with executioncontext, and is a
general-purpose observation.

Reply via email to