changes to MainLauncherBooter and the effect on standalone deployments

[Peter Cousins <pe...@itemfield.com>]

When running applications standalone typically the suggestion has been
to use 

 

    java -jar launcher.jar ${your-executable-jar}

 

However, about a month ago changes were made to MainLauncherBooter that
removed support for supplying a --classpath argument.  

Before this change, this argument could be used to set the classpath for
other dependencies required for the user component inside
"your-executable-jar", which is needed if you usee the suggested -jar
argument since doing so makes the system classloader ignore the contents
of the classpath java command line argument and the CLASSPATH
environment variable.  

 

It was recently noted that --classpath is no longer supported and the
JIRA on it was closed as a doc bug in response to complaints about NPEs.

http://issues.apache.org/jira/browse/TUSCANY-838

 

However, anyone needing to boot their components standalone should add
launcher.jar to the classpath and launch like this instead:

 

  java org.apache.tuscany.launcher.MainLauncherBooter
${your-executable-jar}

 

also, don't forget to put your main class in the jar manifest since
support for the --main command line argument was also dropped.