Re: Avoiding multiple copies of the standalone runtime

2006-11-06 Thread Rick
The samples were designed to just run the ones you were interested and each can require different extenstions. So to make sure you are only running the minimal extensions required by your sample you would also need to remove the ones that were copied for that example when you went to another.

Avoiding multiple copies of the standalone runtime

2006-11-05 Thread Simon Nash
The sample readme.html instructions tell the user to run mvn dependency:unpack to create a standalone distribution under the sample's target directory. This means that each sample will have its own private copy of the standalone runtime, and following these instructions for n samples will

Re: Avoiding multiple copies of the standalone runtime

2006-11-05 Thread David Sanders
curly brackets, e.g., ${env.TUSCANY_HOME}, correctly expands to absolute path. In the following, ${tmp} expands to an absolute path. project name=calculator default=show-cp property environment=env / property name=tuscanyHome location=${env.TUSCANY_HOME} / property name=tuscanySCA

Re: Avoiding multiple copies of the standalone runtime

2006-11-05 Thread David Sanders
curly brackets, e.g., ${env.TUSCANY_HOME}, correctly expands to absolute path. In the following, ${tmp} expands to an absolute path. project name=calculator default=show-cp property environment=env / property name=tuscanyHome location=${env.TUSCANY_HOME} / property name=tuscanySCA