On Nov 17, 2007 6:18 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
<snip> I think that there are two types of "sample dependencies": > > A) samples/store uses implementation-data; implementation-data can > technically run with other databases, but we've selected derby as our > preferred database; derby.jar needs to be on the classpath of the sample > for it to run. > > B) a theoretical example, samples/store uses the Apache batik toolkit to > generate an SVG logo for the store UI, because it's cool; no-other > Tuscany module has that dependency. > > My opinion: > (A) - derby.jar should be in the distro/lib, implementation-data should > have derby as a runtime dependency. > > (B) - simplify samples/store, a technology sample should get to the > point without extra dependency JARs, and if they really can't be avoided > they should be in the sample's directory. > > Those both sound right to me. ...ant
