On 5/14/07, Simon Laws <[EMAIL PROTECTED]> wrote:
snip > > > My suggestion was much simpler, i.e., that we could keep the client > code out of the sample extension jar and include a .class file for the > client code for these 3 samples in the binary distro. This is similar > to what real users will do when developing extensions. > Making this happen is a little complicated from what I can see. I put the client code in the test directory in the first place because I couldn't see a way of excluding it using pom configuration. I've gone back and had a play with it and I still can't see how to exclude a class file from a jar file using the jar plugin. There maybe something that can be done with the assembly plugin but I'm not really familiar with it so maybe one of our Maven experts can help? If we do want to exclude "application" code from the sample extension jar (which I grant you does make sense for the extension samples) then we can either leave the code where it is in the test dir or put it in another sample project. I added this latter proposition because if it's in the test dir then we don't meet the 'run out of the box from a java command line' aspiration that has been expressed previously. Simon
Maybe the extension samples could be treated as special cases that don't need to be usable out of the box from a java command? Most of the samples are demonstrating how to use Tuscany and SCA for applications, and as has been said before in this thread it makes sense to include the tests to show how you can test your SCA based applications. But the extensions are extending the Tuscany runtime so it doesn't seem unreasonable that they aren't quite so simple, How about we don't ship the binaries of these type of samples, also, as the runtime requires maven to build how about not even including Ant scripts for them and just require Maven? ...ant
