Community
Participate
Working Groups
We would like to dynalically determine the temp directory of a remote system and deploy to that directory. Currently this requires the IExecutionEnvironment which does not exist at the current point where the TestExecutionHarness deploys the TestAssets. It could be deployment needs to be moved down in the TEH. The IExecutionEnvironment could then be passed to the ExecutionDeploymentAdapter which could then set the root for deployment as needed. If there is another way of fullfilling this requirement that would be acceptable. Please note we would like to determine the Temp directory of the remote system dynamically instead of requiring the user to enter it in the UI.
Targetted for a future release of Hyades
Targeted to 4.0 by the requirements team. Please create a description document in CVS.
update based on requirements group review
Changes delivered on 3/27/2005 -- Ken please resolve bugzilla entry if this is now complete given the changes I just delivered for you, thanks.
A default deployment root directory is no longer automatically added to the Location during Location creation. When no deployment root directory is supplied in the Location, the code attempts to get a default root directory from a temp directory environment variable. There are three temp directory environment variables which are searched for, in this order, LOCAL_AGENT_TEMP_DIR, TEMP, TMP. If one of these is found, it is used as the deployment root directory. It is also used to build the classpath. If the user adds a ROOTDIR property to the Location, then the one the user added will be used instead of the one from the environment variable. The use of IExecutionDeploymentAdapterExtended is removed. The API is now all contained in IExecutionDeploymentAdapter.
ACTION: Please verify/close this defect.
This has been implemented
