If i understood properly, The webMethods Deployer Dependency default option advantage is ONLY to intiate dependency check manually as to avoid each addition of components to deployment sets. I agree that it would improve performance as you documented.
Let’s consider a case where i want to deploy 3 packages called Package1 to Package3
regardless of dependencies. I am aware of all required dependencies are exist in target server and i DO NOT want to tell the Deployer that dependent componets are exist by selecting EXISTS option for every dependency.
Most cases, we deploy required packages under the assumption that all the dependents are exist at taget server. In this case, the deployer really irritating and time consuming because it will list out dependencies gradually based on my selection.
For ex, for deployment of 3 packages it would show 25 (i assume we have 25 packages which are dependent on these 3 packages) packages (not once, gradually) that are
dependent of these packages.
Is there any feature in Deployer 6.5 that will deploy with out considering dependencies/unresolved references?
I know its just like forced deployment with out considering the consequences/references. But I dont care as I am confident that all the dependent compents are exists on target and dont want to resolve deployer dependency checkings.
Another bug i noticed in Deployer as follows,
I created a project called DemoDeployer6.5 and deleted it. When i attempt to recreate the same project the deployer throws an exception that the project already exist.
I can send the screen shot if you guys want it.