![]() For example: org_alfresco_module_rm_share. It is important that the module ID is globally unique so that it never clashes with other modules when it is installed. The module ID specified in this file will act as a unique identifier for this module. # Depends on net.sf. version 1.0 or later # The following describe dependencies on other modules # to inappropriate versions of the WAR file. # The following optional properties can be used to prevent the module from being added scription=This is my first Alfresco module Uses the records management module to give an example of a typical module.properties contents. The module.properties file itself contains the module id, version, title and description of the module. WhereĮxtension_root is the root directory of the extension, and module_name is the name of the module. The module.properties file should be located in the directory extension_root/alfresco/module/module_name. The module properties file is required by the module service to identify the module, and its details, when it is installed. You can find out more about using the Repository Admin Console here. To view installed Module Packages: You can also use the Repository Admin Console (Enterprise Only) to view installed Module Packages using the following URL: The System Summary includes information about installed Module Packages. In Share Admin Tools, you can use the following URL You can view installed modules if you have Administrator privileges. Share extension that does not includes third-party library Share extension that includes third-party library Platform extension that does not include third-party library Platform extension that includes third-party library ![]() The module.properties file is discussed in more detail here, and the module-context.xmlĬustomization packaging matrix: Extension type It may also include a module-context.xmlįile if the extension uses Spring beans. There are two supported module packaging formats available: Alfresco Module Package (AMP) and Simple JAR Module.Īn extension must include a module.properties file to be identified as a module. There are two main types of extension that can be packaged as modules: Platform and Share extensions. Viewed from the Admin Console or the Share Admin Tools. These modules are registered with Content Services and can be Extensions can be packaged as loadable modules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |