Its fine to have a contribution jar added to the binding-sca-runtime module but the source for any Java classes in there MUST be available somewhere in the Tuscany SVN. So if its not using classes from an existing sample or test then you'll need to make one. Its fine if the contribution has something like extra or modified .composite, wsdl, xsd or other human readable files as it easy enough to look in the contribution jar to view or update those, but thats too hard .class files.
...ant On Thu, Jun 23, 2011 at 4:54 PM, Scott Kurz <sku...@gmail.com> wrote: > Quick question: > > I noticed a bug on the path used by binding-sca-runtime when doing a > cross-classloader (e.g. cross-Contribution) copy. > > Not sure how important it is to people to keep the tests structured > relatively simply... > > I'm thinking I'll add the test to the binding-sca-runtime module and > just check-in a couple contribution JARs as source, since that's > easier to me than trying to build/copy/package things in two JARs. > (I see some modules e.g. 'contribution' checking in JARs as source). > > Kind of ugly not to have the Java as source though... > > Does anyone have a better suggestion on where to add a test for this case? > > Thanks, > Scott >
