Updates to read me for new Mavenized RM build.

git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/DEV/UIAUTOMATION@59399 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This commit is contained in:
Roy Wetherall
2014-01-06 04:20:05 +00:00
parent e21ac0cf9f
commit 12ecf393ce

View File

@@ -1,19 +1,20 @@
== Alfresco Records Management - Development Environment Setup == == Alfresco Records Management - Development Environment Setup ==
Prerequisites Prerequisites
- Maven 3.0.3 (or higher) - Maven 3.0.3 (or higher)
- Eclipse Maven Plugin - Eclipse Maven Plugin (m2e)
- See Maven setup instructions https://ts.alfresco.com/share/page/site/eng/wiki-page?title=Maven_Setup
Initial Setup Initial Setup
- Create a normal project using "create-project"
- Check out RM code into the "code" directory ("checkout https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD")
- Create the tomcat instances using
- "use-tomcat7"
- "use-app-tomcat7"
- Create a normal project using "create-project"
- Check out RM code into the "code" directory (eg "checkout https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD")
- Create the tomcat instances using "use-tomcat7" and "use-app-tomcat7"
Using Eclipse Using Eclipse
- Import projects as Maven projects ("Import > Maven > Existing Maven Projects") - Import projects as Maven projects ("Import > Maven > Existing Maven Projects")
- Browse to the code directory of your project and select "rm-server/pom.xml" and "rm-share/pom.xml". DO NOT select the parent "/pom.xml" - Browse to the code directory of your project and select "rm-server/pom.xml" and "rm-share/pom.xml". DO NOT select the parent "/pom.xml"
- Open the Ant view and add the build files for both modules ("build.xml") - Open the Ant view and add the build files for both modules ("build.xml")
@@ -21,23 +22,25 @@ Using Eclipse
- Now "buildAndDeploy" target can be run which will create the amp file, apply it to the war file and copy the war file to webapps folder. - Now "buildAndDeploy" target can be run which will create the amp file, apply it to the war file and copy the war file to webapps folder.
Summary of available Ant Targets Summary of Available Ant Targets
- assembleIconPackage : Assembles an icons package for the module
- assembleLocalisationPackage : Assembles an i18n package for the module - assembleIconPackage : Assembles an icons package for the module
- buildAndDeploy : Creates the amp file and applies it to the war file - assembleLocalisationPackage : Assembles an i18n package for the module
- prepareEnv : Prepares the development environment (must be run just once) - buildAndDeploy : Creates the amp file and applies it to the war file
- tomcat-start : Starts a tomcat instance - prepareEnv : Prepares the development environment (must be run just once)
- tomcat-start-debug : Starts a tomcat instance in debug mode - tomcat-start : Starts a tomcat instance
- tomcat-stop : Stops the running tomcat instance - tomcat-start-debug : Starts a tomcat instance in debug mode
- tomcat-stop : Stops the running tomcat instance
Summary of available Internal Ant Targets Summary of Available Internal Ant Targets
- alfresco:amp : Creates the amp file using alfresco maven plugin
- alfresco:install : Installs the amp file to the war file - alfresco:amp : Creates the amp file using alfresco maven plugin
- cleanTarget : Deletes the "target" folder - alfresco:install : Installs the amp file to the war file
- copyDBDriver : Copies the DB driver - cleanTarget : Deletes the "target" folder
- copyDevContextFile : Copies the dev-context.xml file - copyDBDriver : Copies the DB driver
- copyWarFileToTomcat : Copies the war file (amp applied) to the webapp folder - copyDevContextFile : Copies the dev-context.xml file
- copyWarFileToTomcat : Copies the war file (amp applied) to the webapp folder
- deleteExplodedWar : Deletes the exploded war file - deleteExplodedWar : Deletes the exploded war file
- deleteWarFile : Deletes the war file - deleteWarFile : Deletes the war file
- fetchWarFile : Gets the "original" war file - fetchWarFile : Gets the "original" war file