- ANT MIGRATION TOOL SALESFORCE FOR MAC HOW TO
- ANT MIGRATION TOOL SALESFORCE FOR MAC UPDATE
- ANT MIGRATION TOOL SALESFORCE FOR MAC FULL
- ANT MIGRATION TOOL SALESFORCE FOR MAC PASSWORD
Or fiddle with the Classpath tab in the external tool configuration. The IDE console will suggest where you can place the ant-salesforce.jar file. Yes, the above fails because the ant-salesforce.jar is not on the classpath. select retrieveUnpacked (same as we did above on the command line).Then select the External Tools Configurations.Click on the external tools button in the top. Notice the build.xml etc files are listed (if you have no filters). Return to the IDE and selection the Production project.
ANT MIGRATION TOOL SALESFORCE FOR MAC HOW TO
Next: how to use the Ant tool from within IDE The deploy might be faster without this flag. This strongly suggests there is a problem with the IDE.īy using the -v flag I get to see all the tests that run. It runs a lot quicker that using the IDE. Now run the ant tool but this time with the deployUnpackaged target ant -v -lib. Notice that I have changed deployRoot to src I am going to see what happens now.Īlso make one more edit in the build.xml file. The new normal with any change like this, for me, is a 30 to 40 minute hurry up and wait when I deploy it to production. Next make some small change to the class. The result is a download of the contents in the package. Tells Ant to run the contents of that section of the ant file.
" says to include the jar file located in this directory. It is optional but helps you understand what is going on. From the command prompt and after changing directory to get to ProdMini run this: Ready to download the files from the server. My project has one Apex class and one trigger.
ANT MIGRATION TOOL SALESFORCE FOR MAC UPDATE
So update the IDE and get the latest Migration Tool. I don't know what happens if these are not in sync. The version number depends on the version of ant tool and IDE. This sets up the download from Production to your project of anything contained in the package.xml file. RetrieveTarget="src" unpackaged="src/package.xml" RetrieveTarget="retrieveUnpackaged" unpackaged="unpackaged/package.xml" Next edit the sample build.xml and make these small adjustments.
ANT MIGRATION TOOL SALESFORCE FOR MAC PASSWORD
Edit the build.properties and adjust the user name and password (append your token). More on this file later.Ĭopy ant-salesforce.jar, build.xml, build.properties to ProdMini. All you really need at this point is the package.xml file. In here you will find a package.xml file and subdirectories like classes. All IDE projects have a subdirectory called "src". ~/Documents/salesforce/workspace/ProdMiniĪnd call it ProdMini for short.
ANT MIGRATION TOOL SALESFORCE FOR MAC FULL
Instead they are a full copy of all the classes, etc that I can use to check into a source control program.įor this discussion I will do everything in The Mini projects hold just the classes, triggers, etc that I need for the current work.
The Test project are for developing on a sandbox and the Prod project are for Production. For example, TestMini, TestFull, ProdMini, ProdFull. Let's assume our IDE workspace is located Getting these is not hard and the documentation provides the instructions. My system is a Mac 10.6 so I have Java and Ant installed. Get the tool via the Salesforce UI under Settings. These steps are mainly about how to adapt the tool to work within the IDE file structure and to even use and edit it inside the IDE. The following are my steps to use this tool on myį IDE projects.
Using a command line tool can be a learning curve that we might not This post described my experience and one suggestion is to use the Ant Migration Tool. Thanks to the folks who post comments on ! I love the stackoverflow communities. But recently, I have found deployment time to be excessive (30 to 60 minutes). Then at Dreamforce 2011 I learned to make smaller projects and this really helped. As mentioned in previous posts I found that the time to deploy got really long.