>> I see no dependency or reason for it to be part of sesat-kernel > > There will be dependency from where we want to use it. Currently it is > used in search-command-config-spi. Except from that, I don't mind moving > it or renaming it.
That's fine. Our other commons libraries: commmons-ioc, commons-reflect, commons- log4j; are used throughout sesat-kernel. The point being that the Interpreter is nice clean code very isolated of dependencies that should form it's own stand alone library. sesat-commons is the place for it then in my opinion. Of course you could host it anywhere you like but sesat-commons is set up ready for you :-) ~mck -- "Wars of nations are fought to change maps. But wars of poverty are fought to map change." Muhammad Ali | www.semb.wever.org | www.sesat.no | www.sesam.no | _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
