From: Wolfgang M. <wol...@ex...> - 2010-08-12 17:27:13
|
> Sorry for the conflicting statements, even the core-dev's have > different ideas - hence this eXist development mailing list. For the > time being it really does not matter where you put them as long as it > works, right ;-) Sure, it's not a problem to move some jars around. > But when it comes to tidying up then following existing convention > extensions/betterform/lib would seem the right place IMHO - but I have > no idea how this translates at runtime i.e. will they be available on > the classpath? I just dont know! Even if we enable betterform by default in the distribution, it would still be good to make it easy for people to disable it and remove the jars they don't need. I think the general convention should thus be: lib/extensions - contains eXist extension code extension/.../lib - contains libraries an extension depends on We followed this convention for the Lucene as well as the spatial extensions.I would thus suggest to put your libs into extensions/betterform/lib, except for those libraries needed by other parts of eXist as well (saxon should go into lib/endorsed). The classloader is not a problem: you can extend src/org/exist/start/start.config to load jars form extensions/betterform/lib by default. It's not a problem if the jars are not found. Wolfgang |