ST - Building and deploying the tool

Pre-flight check

  • ~/build.properties
  • Tomcat exists
  • Tomcat is stopped

Build, Deploy, Run

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Apr 22, 2008

    rk tumuluri says:

    This step is incomplete and confusing. I did the following to "deploy". (My env...

    This step is incomplete and confusing. I did the following to "deploy".
    (My environment WindowsXP Pro, Jdk 1.5.0_14, Maven 2.0.9, Sakai 2-5-0, Subversion 1.4.6, apache-tomcat-5.5.23, MySQL 5.0)

    1) c:\> mvn clean install (for a clean build)
    I had to do this 3-4 times, during which the #errors kept reducing. It appears from the build logs that the process of finding-downloading various libraries (jars etc) and populating the maven repositories (at M2_REPO=c:\documents and settings\ranki\.m2\repository ) is somewhat buggy. The dependencies are laid out in such a manner that one-pass of the build does'nt cut it. Is this solvable ?. At least there seem to be no dreaded circular dependencies. At the end of this build several "jars" and "wars" were created. They seem to be spread around various directories though.

    2) c:\> mvn sakai:deploy -Dmaven.tomcat.home=c:\apache-tomcat-5.5.23. All the "war files" related to various tools got copied to c:\apache-tomcat-5.5.23\webapps. On starting the tomcat server, the sakai application got loaded correctly and the application was usable.

    3) The files mentioned on this page under the heading "Pre-flight check" are not quite relevant it seems. Any clarifications ?.

    /rk