Include, Exclude Filters together?

Hi,
I was wondering if I could use a combination of include and exclude filters. Let me explain the problem we are experiencing. Currently we are doing a directory comparison deployment with few include filters that specify all the extensions that need to be deployed. From now onwards the target is going to get some content from another source for one particular folder. Obviously that directory is going to be deleted with subsequent deployments as we are using doDeletes option. I am thinking of using include filters at source side and exclude filters on target side. Will it work or is there any other way of achieving what I am after?

Thanks a lot
-H

Find more posts tagged with

Comments

Adam Stoller

I believe that should work - but I suggest you try running the deployment from the command line with the '-sim' flag in order to verify what will / won't happen when you actually run it for real.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

herald10

It doesn't work. It still deletes the files specified in the exclude filter. I am using targetRules to specify the exclude path. Does it matter?

Thanks a lot
-H

Adam Stoller

Can you post your deployment configuration file (as an attachment)?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

herald10

Please find my deployment configuration file in the attachment.

Thanks a lot
-H

Adam Stoller

Whoops my brain was only half-awake when I responded before. The exclusion would have to be listed in BOTH the source-side and target-side filter clauses.

If listed just in the source-side clause - it's as-if the affected files didn't exist on the source side and a deletion request will be made for the target-side (with doDeletes enabled).

If listed just in the target-side clause - it's as-if the affected files didn't exist on the target side and, if they exist on the source side, they will be deployed every time.

If listed in both the source-side and target-side clauses - they are treated as non-existant on the source side *and* non-existent on the target-side and thus there is no deployment and no deletion.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com