{"id":4158,"date":"2015-01-01T02:54:21","date_gmt":"2015-01-01T02:54:21","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=4158"},"modified":"2015-01-01T02:54:21","modified_gmt":"2015-01-01T02:54:21","slug":"auto-generate-package-xml-using-ant-complete-source-code-and-video","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/auto-generate-package-xml-using-ant-complete-source-code-and-video\/","title":{"rendered":"Auto generate Package.xml using Ant – complete source code and Video"},"content":{"rendered":"

If we\u00a0want to use Ant\u00a0Migration tool to fetch Salesforce Organization metadata info or to deploy some changes to Salesforce, we need to create “package.xml<\/strong>” manually or take help of eclipse. wildcard character (*) doesnt work with some components like report, emailtemplate, dashboard and document. Package.xml must needs to have folder name and files inside folder name. \u00a0After getting package.xml from eclipse, what if some folder is added into Organization ? We need to update “package.xml” again with help of eclipse or do it manually. Therefore I wanted to automate generation of package.xml completely and came up with this article and below workaround.<\/p>\n

I would be using Ant\u00a0to generate “package.xml” with below steps<\/p>\n

    \n
  1. get Ant\u00a0Migration tool jar from here<\/a><\/li>\n
  2. get AntContrib from here<\/a><\/li>\n
  3. create basic template of “package.xml” with placeholders in place of Report, Dashboard, EmailTemplate and Document, sample here<\/a><\/li>\n
  4. create Ant\u00a0Macro to replace placeholders<\/li>\n
  5. create second Ant\u00a0Macro to fetch all folders available using Metadata API (using sf:listMetadata)<\/li>\n
  6. create third Ant\u00a0Macro to fetch files inside each folder using Metadata API (using sf:listMetadata)<\/li>\n<\/ol>\n

    <\/p>\n