definition in deployment

niniti

I dont understand one basic thing in deploymentConfiguration.

If there are more than one definitions in deploymentConfiguration we can use any definition in "execDeploymentTask" element. If we are using only one definition of many definitions , then whats the point in having multiple definitions in same file ? How can I use other definitions ? Is there a way, I can configure other definitions for different situations automatically ?
Why not use different deploymentConfiguration for different definitions ?

Adam Stoller

I dont understand one basic thing in deploymentConfiguration. If there are more than one definitions in deploymentConfiguration we can use any definition in "execDeploymentTask" element. If we are using only one definition of many definitions , then whats the point in having multiple definitions in same file ? How can I use other definitions ? Is there a way, I can configure other definitions for different situations automatically ? Why not use different deploymentConfiguration for different definitions ?

Did you ever think of going for training?
If you have multiple definitions you could have multiple execDeploymentTask's (1:1) - or you could have a single execDeploymentTask that used a command-line parameter to determine which of the definitions it should use.
Or, as you suggest, you could have a bunch of separate configuration files each with one definition and one execDeploymentTask. However, if you need to deploy files to multiple locations and you want to do it all within a single invocation of OpenDeploy (presumably transactionally) then having them all in the same configuration file (with multiple execDeploymentTask's) makes sense.