OW2 Consortium
Search OW2 Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | exoplatform List | April 2007 Index

<--  Date Index  --> <--  Thread Index  -->

Re: [exoplatform] WebOS


Hi,
 
Thank you.
 
A beta version is scheduled by the month of may.
 
I'm including below a documentation initiated by Tuan on how to build the WebOS. We should publish it on the wiki soon.
 
1.1; Create base structure
--------------------------
  - Create a "java" directory. We will call it $EXO_BASE_DIRECTORY.  By default  the $EXO_BASE_DIRECTORY
    directory should be in your $HOME directory in linux  and in D:  drive on window
 
  - Install jdk  and maven2 in  the java directory

  - Create exo-dependencies  and  exo-working directories in the java directory
 
  - Copy a  template tomcat directory to  exo-dependencies. the directory name  should have the form
    tomcat-${version}. 

  - By the end  You  should have the following directory structure

      java/
          exo-dependencies/
                           tomcat-${version}
                           jboss-${version}
             
          exo-working
          jdk1.5
          maven2

1.2; Check-out
--------------

  - Go to your $EXO_BASE_DIRECTORY and run the following command :

      svn co svn+ssh://exo@xxxxxxxxxxxxxxxxxxxxxxx/svnroot/exoplatform/projects eXoProjects

1.3; Configure environment
--------------------------

- Copy $EXO_BASE_DIRECTORY/eXoProjects/tools/trunk/config/maven2/template- settings.xml  your
   $HOME/.m2/settings.xml  and adapt the  configuration to your environment. If you do this ,
   the maven2/conf/settings.xml will be ignored. This step is  mandatory  for  the window  environment.
   For the linux or cygwin  enviroment you can  bypass  this step  as the exoenv.sh script can copy and
   configure  the settings.xml file automatically for you

- On Linux  or Cygwin Environment

   * Copy $EXO_BASE_DIRECTORY/eXoProjects/tools/trunk/build/src/main/resources/linux/exoenv.sh
     to your $HOME or $EXO_BASE_DIRECTORY directory. Backup the old one if you have one.

- On Window And DOS Environment

   * Copy $EXO_BASE_DIRECTORY/eXoProjects/tools/trunk/build/src/main/resources/window/exoenv.bat
     to your $HOME or $EXO_BASE_DIRECTORY directory. Backup the old one if you have one.

- Update The Configuration

   * Edit the exoenv.sh or exoenv.bat file to adapt it to your environment. You should only
     have to change the PORTABLE_DIR variable at the beginning.

   * Run the command to setup the environment:
    
     On linux or cygwin: source exoenv.sh

       To check that it has worked well, open the $EXO_BASE_DIRECTORY/maven2/conf/settings.xml
       and check that the file corresponds with your environment, especially the definition
       of the repositories.

     On window and dos  prompt: exoenv.bat

1.4; Build and deploy
---------------------
Usage the exobuild command:

  exobuild --product=[portal,ecm,groupware] [--update]  [--build-dependencies] [--deploy=tomcat,jboss,jonas]

  Options:
    * --product            is mandatory. The possible names are portal, ecm, groupware, all
    * --update             is optional. If you add this option, exobuild  will make a
                           svn update before it builds
    * --build              is optional. If you add this option, the exobuild command
                           will compile and install the sub projects of the product,
    * --build-dependencies is optional. If you add this option, the exobuild command
                           will build the dependant modules of the product,
                           for example: kernel, core, portal...
    * --deploy             is optional. The possible names are tomcat-server, jboss-server, and
                           jonas-server. If you enter only --deploy, the tomcat-server will be used
    * --database           is optional. This option must use with the --deploy option. The possible
                           values are hsql, mysql, oracle, postgres, derby and mssql
    * --ask                is optional. This option is used with --database option. it allow you to
                           enter the connection url , username and password of the database server


  For Example:
 
     exobuild --product=ecm --build --build-dependencies --deploy

  Will build kernel, core, portal, jcr , pc and ecm  and then deploy

1.5; Launch Tomcat
------------------

  On Linux or Cygwin Environment

     - Go to $EXO_BASE_DIRECTORY/exo-working/exo-tomcat/bin directory

     - Change the rights on .sh files to make them executable : chmod +x *.sh

     - Run the command : eXo.sh run

1.6; Access The Portal
----------------------------

  - Open  Firefox or IE6/7

  - Enter http://localhost:8080/ecmportal/ in the address bar

 
 
 
 
HTH
-Brice.
 
On 4/16/07, Andrea Bardone <andreabardone@xxxxxxxxx> wrote:
Hi all,
I try to use eXo WebOS: it's wonderful!

I'd like build all source but I can't do it and I read that the build system changed a little bit from old version.

Could you tell me when it will be possible build WebOS version from source?

And...  could you also tell me when it will be released next version of webos ? Will it be a  beta version?

Thank you very much in advance.

Andrew



------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
http://i-mode.wind.it/





--
You receive this message as a subscriber of the exoplatform@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto: exoplatform-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws




--
Brice Revenant
eXo Platform SAS

<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 2006-2007, OW2 Consortium | contact | webmaster.