On Wed, Nov 25, 2009 at 11:40 AM, Simon Laws <[email protected]> wrote: > +1 to being explicit about contribution location. I would favour an > approach where sample projects simply produce contributions. They can > then we used by launchers of various flavours. > > command line > embedded > domain > > We would though still need to include tests for the samples. We could > either stick with unit tests or use the itests. We should use a > mixture of a limited number of approaches to show best practice for > each situation. > > Simon >
Ok that all sounds fine to me. Shall we explore what that would look like - I've added samples/helloworld which is a plain SCA contribution with a unit test that doesn't use any Tuscany, and an itest/samples/helloworld which is an integration test for the helloworld sample that runs it in Tuscany. Is that the type of thing most of the samples should be? Should the sample be a jar instead of a zip? Should we have a plugin for running the itest instead of manually createing a runtime along the lines of how things like webapps are usually tested? ...ant
