Timeline for Ant Deployment To New Dev Org
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2014 at 16:45 | vote | accept | powlo | ||
| Jun 13, 2014 at 17:15 | answer | added | Mike Ginou | timeline score: 0 | |
| Jun 12, 2014 at 15:00 | answer | added | Jason Lantz | timeline score: 1 | |
| Jun 12, 2014 at 11:40 | comment | added | Davin Casey | Yes but when you retrieve the unmanaged package a package.xml will be included, so you don't have to use one from Eclipse etc. | |
| Jun 12, 2014 at 11:39 | comment | added | powlo | But I have to have a package.xml to deploy. Here's what happens if I try and deploy without a package.xml in the "deployRoot" directory: 1. package.xml -- Error: No package.xml found | |
| Jun 12, 2014 at 10:58 | comment | added | Davin Casey | I have found retrieving components via package.xml to be troublesome & tedious to maintain, so we have switched to using unmanaged packages in the source org. Simply populate the package with the components to be migrated, then retrieve using the package name, not an xml file, and then deploy as normal. As for the errors you're getting, most of them looking to be org. setting related - Account Teams etc. etc. | |
| Jun 12, 2014 at 10:28 | history | asked | powlo | CC BY-SA 3.0 |