From: Dannes W. <da...@ex...> - 2010-02-17 09:32:46
|
Hi, On Wed, Feb 17, 2010 at 10:25 AM, Adam Retter <ad...@ex...> wrote: > > should we separate modules to have jar per module? > > Ideally yes. Each extension module should have its own Jar. > Let's stay practical here :-) A jar file containing just 5 or 8 classes is a bit too in-efficient probably. Don't think of the extra work you'll get (create and more important: maintenance) in the software archive: build.xml dependencies etc..... Having extensions\modules split would introduce 20 !!!! new jar files. Please no, let's NOT do that. Being pragmatic, I released a jar file on http://code.google.com/p/existdb-contrib/downloads/list with all modules enabled. That is easy to use :-P and user friendly D. -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |