mirror of
https://github.com/Alfresco/alfresco-community-repo.git
synced 2025-07-31 17:39:05 +00:00
b79cb65c0b
40344: RM-477: RM 2.0 does not work with SOLR
* first pass at supporting SOLR in RM2
* currently requires reimplementation of permissionServiceImpl due to visibility of methods and member variables
* job execution delayed to try and prevent start up errors
* fetchSOLR task added to gradle to retrieve SOLR zip from Maven (could do with some scripts to help with setup for module)
* TODO more testing and refinement of solution
40383: RM: Fix unit test
40656: Updated ReadMe.txt
40696: RM-439: Folders have no File to... option
40778: RM-434: The user has all rights for audit once "Access Audit" capability is added to him
40784: RM-482: RM .classpath files have local library references
40785: RM: Remove .settings dir for Eclipse projects
* See RM-482
40786: RM: Set svn:ignore for generated eclipse project files
40800: RM-434
40904: It was not possible to edit/delete a custom meta data
40920: Disabled the delete button for custom meta data
40948: RM-438: Custom metadata fields and Special Types aren't available in Email Mappings
41021: RM-438: Custom metadata fields and Special Types aren't available in Email Mappings
* ensured the 'group' information was being passed to property-menu (so the custom and dynamic record meta-data is available)
* also tweaked audit in the same way
* removed code to add custom meta-data props as no longer needed
41023: Merged HEAD to BANCHES/V2.0-BUG-FIX:
40944: Adds Spanish RM translation
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@41024 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
== Alfresco Records Management - Development Environment Setup ==
Prerequisites
- Gradle 1.0 milestone 8a (optional unless native gradle support is required)
- Alfresco Repository 4.0.1 (or higher). Specifically you need the alfresco.war and share.war files.
- Any prerequisties required for an Alfresco installation, including Java 1.5, Tomcat and a suitable database.
NOTE: throughout these instructions we will use the 'gradlew' wrapper command. This wrapper command downloads the required Gradle libraries automatically. Should you prefer to use the native 'gradle' command instead you will need to install Gradle manually.
Initial Setup
- Checkout Records Management code from https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD
Note: the RM branch structure reflects the main repository branch structure, so HEAD is the current development branch and BRACHES contains the release branches.
- Run "gradlew fetchWarFile". This will use Maven to download the dependant Alfresco War's, currently version 4.0.1
- Run "gradlew amp" in root directory. This will unpack the dependancies, build the RM source and finally assemble the RM amps.
Note: the first execution of this task may take serveral minutes, because it will unpack the required build dependancies from the alfresco and share WAR. It will also pull any external dependancies from Maven or
- You will not find rm-server\build\dist\alfresco-rm-2.0.amp and rm-share\build\dist\alfresco-rm-share-2.0.amp ahve been built.
Using Eclipse
- Run "gradlew eclipse". This will generate the eclipse project files.
- Start Eclipse in the usual way.
Note: make sure the WAR dependancies have been exploded before opening Eclispe.
- Import projects found in rm-server and rm-share directories.
Deploying the RM AMPs
- Set the envoronment variables TOMCAT_HOME and APP_TOMCAT_HOME to the home directory of the repository and share Tomcat instances respectively.
NOTE: these can be the same tomcat instance, but it is recommended that two are used.
- Configure your repository Tomcat so that your repository.properties settings will be successfully picked up when Alfresco is started.
- Run "gradlew deployAmp" in the root directory. This will use the MMT to apply the RM AMPs to the Alfresco and Share WARs respectively. The modified WARs will then be copied to the set Tomcat instances, cleaning any exisiting exploded WARs.
- Start Tomcat(s).
For users of the Alfresco DevEnv
- 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)
- The devEnv will automatically set the TOMCAT_HOME and APP_TOMCAT_HOME environment variables to point to the Tomcat instances created by the use-tomcat6 and use-app-tomcat6 scipts. Magic!
- Copy the JDBC driver to <TOMCAT_HOME>/lib/
- You can use the dev-context.xml generated for you to configure the repository. Place it in <TOMCAT_HOME>/shared/classes/alfresco/extension and <PROJECT_NAME>/code/rm-server/config/alfresco/extension.
Summary Of Available Gradle Tasks
Note: All these tasks can be executed in the root directory or in either of the sub-project directories.
Note: Use the command "gradle <taskName>" when executing.
Note: The RM Gradle scripts import the standard "Java" package so those associated standard tasks are available, for example "jar", "compileJava", "clean", etc
- explodeDeps : checks for existance of the projects dependant WAR (either alfresco.war or share.war). If not already exploded, unpacks the required depedancies from the WAR files.
- cleanDeps : cleans the projects exploded dependancies.
- amp : builds the projects AMP and places it in build/dist.
- installAmp : installs the AMP into a copy of the projects dependant WAR using the MMT.
NOTE: the installed WAR can be found in build/dist.
- deployAmp : depolys the project AMP to the configured Tomcat instance.
- fetchWarFile : fetches the dependant Alfresco WAR files
- eclipse : generates eclipse projects for repository and share projects