-
Notifications
You must be signed in to change notification settings - Fork 0
Creating a Build Manually
(These instructions are incorrect at the moment. They were accurate when the sources were kept in a Subversion repository and need to be updated to reflect a Git repository, and the automatic build scripts probably need to be updated.)
This page describes how to run the Maqetta build scripts manually. Developers sometimes need to do manual builds for one-off development/debugging reasons or because they can't wait until the next automatic build. There are also automatic build scripts that run at a regular time each day or multiple regular times per day.
The manual build scripts prepare a release build, doing things such as combining zillions of separate JS and CSS files into a much smaller number of consolidated (but bigger) files and minifying the files. The build scripts also are necessary in leverage HTML5 application cache. The build scripts also do some preparatory work such as automatically injecting the build number into the "About Maqetta" dialog.
Your machine needs the following to create builds:
- 64-bit JVM. To see if you have a 64-bit JVM, open a shell window and type "java -version".
- Command-line "svn" on your PATH. To see if you have command-line "svn", open a shell window and type "svn".
- Launch Eclipse
- Create temp directory, e.g. /Maqetta/temp/VERSION
- Update all projects with latest from HEAD
- right click on the davinci.product & davinci.core projects and select "Refresh" (do this for all projects?)
- right click on davinci.product and select "Export"
- Under "plugin development" select "Eclipse Product"
- In the next dialog, use these settings:
- configuration: /davinci.product/DavinciServer.product
- root directory: eclipse
- Synchronization: not checked
- destination: /Maqetta/temp/VERSION
- export source: unchecked
- generate metadata: unchecked
- allow for binary: checked
- The above process launches Dojo build scripts. To verify that the build scripts ran successfully, look inside the davinci.core JAR and look at build.out in a text editor and see if there are any error messages. If successful, this file should have hundreds of lines in it.
- after export copy the following files from the davinci.product plugin and place into /Maqetta/temp/VERSION/eclipse:
- maqetta.local.mac.command
- maqetta.local.win.bat
- maqetta.server.mac.command
- maqetta.server.win.bat
- on mac, make sure the these files all have "x" execute permission by going into Terminal and issuing a "chmod a+x maqetta.local.mac.command maqetta.local.win.bat maqetta.server.mac.command maqetta.server.win.bat"
- For Mac builds, it appears to be necessary to manually update the configuration/config.ini file. Somehow the build process isn't updating that file and a bogus config.ini file is being used.
- in windows explorer, select all of the files in /Maqetta/temp/VERSION/eclipse, and do "add to zip" (want the contents of /Maqetta/temp/VERSION/eclipse as the root of the archive. (On Mac, in Finder, open the /Maqetta/temp/VERSION folder, select "eclipse" and with context menu issue "compress command to create eclipse.zip.)
- rename the zip file as appropriate (e.g., to maqetta_preview_N.zip)
If you want to do this on your own machine, check out the following projects:
- davinci.war
- org.eclipse.equinox.http.servletbridge
- org.eclipse.equinox.server.core
- org.eclipse.equinox.server.servletbridge
- org.eclipse.equinox.servletbridge
- org.eclipse.equinox.servletbridge.extensionbundle
- synchronize all projects with repository
- right click on davinci.war and select "Export"
- Under "plugin development" select "Eclipse Product"
- In the next dialog, use these settings:
- configuration: /davinci.war/DavinciWar.product
- root directory: WEB-INF
- Synchronization: not checked
- destination should be "Archive file"
- export source: unchecked
- generate metadata: unchecked
- allow for binary: checked
- after export, rename the resulting .zip to .war