BuildDesk Quick Reference

Technologies behind BuildDesk

BuildDesk uses the following tools to automate build processes:

  • Apache Ant - to execute build scripts
  • BuildDesk's own windows launcher - to find correct JVM, show native splash, pass parameters to VM and run it
  • NSIS - to create Windows-native installers
  • Proguard - to perform code obfuscation

What gets generated

If your project is named, say, "idea", BuildDesk will generate 4 files for you:

  • idea.xml - the script file which gets executed by Ant
  • idea.xml.zip - a storage file that contains generated binary data for your application and some jars needed for successful build. This file is required by idea.xml
  • idea.bdp - a BuildDesk project where all meta-data is saved
  • idea.xml.workspace - a standard Java property file where you can re-define some properties
So why generate idea.xml.zip and all those additional files? There are two reasons:
  • Whatever build data is needed, we always deal with those 4 files. BuildDesk will put stuff there on it's own and it's easier for you to manage constant number of files. If you use version control, you know why
  • All you need to build you project from command line is idea.xml, idea.xml.zip and optionally idea.xml.workspace You don't have to patch your Ant, put something to it's "lib" folder, modify "ANT_OPTS" & etc. It will just work