Page History

Tuscany Samples Requirements

There are two main motivations for this:

1) consistency across samples to make it easier for users to understand how to use Tuscany. Ideally once a users understands one type of sample they would be able to use similar samples without having to read any more doc.

2) simplification of the release process. It has proven to not scale with everyone able to add any old sample they happen to like and have that require for ever more that it is manually reviewed at every release and any issues be release blockers.

So based on those we decided to move all the existing samples out of the main trunk build where they can be developed and use a consensus base review-then-commit approach to add samples to the main trunk build.

We can't be completely prescriptive on the requirements of any and every new sample but some common themes have been:

consistent build

• eg using the base + extension approach for the tuscany dependencies

Unit test for

• showing basic functionality of the sample
• providing a continuous integration mechanism

...

• instructions on how to run the sample using the shell
• information on the Tuscany Maven archetype

Examples

• http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/contribtrunk/samples/getting-started/helloworld-contribution/^{Image Modified}