Difference between revisions of "Manual Installation From Trunk"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Installation) |
(→Installation) |
||
| Line 15: | Line 15: | ||
* Create a folder to hold the source code, for e.g, adempiere-source | * Create a folder to hold the source code, for e.g, adempiere-source | ||
* Check out source from trunk into the folder created in previous step | * Check out source from trunk into the folder created in previous step | ||
| − | ** svn co https://adempiere.svn.sourceforge.net/svnroot/adempiere/trunk | + | ** svn co https://adempiere.svn.sourceforge.net/svnroot/adempiere/trunk |
| + | *** you might need export LC_ALL=en_US.UTF-8 (or any other UTF-8 language) before svn checkout | ||
* cd into the trunk/utils_dev folder created by the checkout command | * cd into the trunk/utils_dev folder created by the checkout command | ||
* Create mybuild.properties from build.properties | * Create mybuild.properties from build.properties | ||
Revision as of 14:20, 24 March 2007
Contents
Pre-requisites
- JDK1.5.x
- JAVA_HOME variables declared
- One of the supported database
- Oracle 10g
- Oracle XE
- Postgresql 8.1 and above
- SVN client
Installation
- Create a folder to hold the source code, for e.g, adempiere-source
- Check out source from trunk into the folder created in previous step
- svn co https://adempiere.svn.sourceforge.net/svnroot/adempiere/trunk
- you might need export LC_ALL=en_US.UTF-8 (or any other UTF-8 language) before svn checkout
- svn co https://adempiere.svn.sourceforge.net/svnroot/adempiere/trunk
- cd into the trunk/utils_dev folder created by the checkout command
- Create mybuild.properties from build.properties
- Edit mybuild.properties to suit your environment
- At trunk/utils_dev, execute RUN_build.bat for window or RUN_build.sh for linux
- cd to the local deployment folder created by the build process ( the env.ADEMPIERE_HOME entry in mybuild.properties )
- Execute the setup script RUN_setup.bat for window or RUN_setup.sh for linux
- You might need to execute chmod +x RUN_setup.sh for linux
Notes
Oracle
- The setup script have been changed to use the EZCONNECT naming method instead of TNSNAMES. Open your Oracle Net Manager, under profile -> Naming, make sure EZCONNECT is one of the selected methods. Alternatively, verify that the SQLNET.ORA file have the following entries: NAMES.DIRECTORY_PATH = (EZCONNECT,TNSNAMES)
