
This process can take quite long time (up to 25 min) depending on hardware configuration.

While going through the console application, DO NOT change the default context name which is openbravo. Note: More about setup ant task can be found at Openbravo.properties#Edition.Īs a result of these actions a new file Openbravo.properties, containing specified settings, will be created in config subdirectory. The invocation of this ant target will compile and execute automatically a console application.By going through the console application provide all requested information and at the end, select Accept to apply the changes and close the application. For that, go to the directory with the working clone of the repository and execute: This can (and in fact must) be done via a console application which has to be compile first. Tomcat installation directory, database connection details, etc. So, first of all you have to configure the Openbravo by specifying some general properties, e.g. The Openbravo installation is performed in several steps. If you want to build the latest stable release:įor Openbravo developers, you should work with the pi repository: It is also highly advisable to clone the repository into a destination directory which is outside of Eclipse workspace. As it's explained in the guide it's normally considered as a good practice to have a pristine clone and working one, so we would strongly encourage you to follow that 'rule'. The detailed procedure of the source code check out is described in Mercurial Manual for Openbravo Developers. There is no any restrictions on the read access so you wouldn't need any credentials to access the repository.

The source code can be checked out using any Mercurial client.

