Topic - Distribution and Packaging of Tuscany Java SCA
Status - Being discussed

Problem that we are trying to solve
Today, users who embed Tuscany get one distribution packgae that includes everything. Users may not need all that is in the distribution package.
Functional packages that are geared towards users' need will improve consumability.

Things to Consider

• Packaging is a release distribution discussion only.
• Make it easy for users.
• Avoid providing huge chunks of uneeded code to users if they do not need it
• Some users may want it all, consider that
• Define what are the potential user groups who would want to download Tuscany.

Suggestion
One potential breakdown for packaging:
1. tuscany-all.zip -

• user type: Wants to pick up the whole Tuscany
• Can include: Everything

2. tuscany-core.zip -

• user type: Tuscany-core will be the base for tuscany-web, tuscany-jee, tuscany-process. Can this be packaged with those?
• Can include: core assembly model and runtime Java APIs, Java components

3. tuscany-web.zip -

• user type: Web development
• Can include: WS binding, Web 2.0 bindings, Scripting components, Widget components

4. tuscany-jee.zip -

• user type: JEE app integration
• Can include: EJB, RMI and JMS bindings, Spring components

5. tuscany-process.zip

• user type: For process development
• Can include: BPEL and XQuery components

Needs further thinking
How to handle the various runtimes? For example, how to make this work with specific application servers. Is there additional code needed?