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 >
We do have examples where contribution jars are held in svn but generally they are built from modules that are elsewhere in svn. It's useful in case we need to rebuild the contributions. Is that the case here? Is the source somewhere in svn? Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
