>
> I think we need to decide once and for all what we're going
> to do about launchers. It seems complicated at the moment.
>
AFAICT the commands we currently have are, in no particular order:
1 tuscany.bat
2 mvn tuscany:???
3 org.apache.tuscany.sca.launcher.LauncherMain
4 org.apache.tuscany.sca.node.launcher.NodeLauncher - for JSE
5 org.apache.tuscany.sca.node.equinox.launcher.NodeLauncher - for OSGi
6 creating a war and dropping it into a container
7 adding the contribution to the tomcat integration
8 org.apache.tuscany.node.NodeFactory - for embedded JSE operation
9. there is a mvn surefire thing that runs JUnit tests in OSGi IIRC
10.???
the classpath mechanisms we currently have are
1. ${tuscany.home}/features/tuscany-sca-manifest.jar
2. ${tuscany.home}/lib/tuscany-base-nodep.jar
3. org.apache.tuscany.sca.node.equinox.launcher.NodeLauncher is
sentivite to environment and loaded bundles it finds in distro
4. org.apache.tuscany.sca.launcher.LauncherMain I think this does
automatic creation of classpath but I don't know how
5. ${tuscany.home}/modules/*.jar
6. ${tuscany.home}/features/configuration/config.ini - can we read
into OSGi to have it load bundles
7. mvn dependencies - direct to modules
8. mvn dependencies - based on features
9. ???
I think we need to map these options and make a clear recommendation
(and demonstrate in our samples) what people should do in the
following situations...
A. running a contribution from the command line
B. running a contribution from Maven
C. running a contribution from JUnit
D. running a contribution from eclipse (or any other IDE)
E. running a contribution from Ant
F. running a contribution from OSGi
G. running a contribution from a webapp
H. running a contribution from Tomcat
What have I missed?
Simon
