MidCOM component manifest

1. Example of config/manifest.inc

config/manifest.inc is one of the required parts of each MidCOM component. MidCOM component manifest is used to

• Give name of the component
• Give short textual definition of component
• Define possible usage of MidCOM cron service or watchers
• Specify PEAR package details

Example of config/manifest.inc

'name'              => 'net.nemein.calendar',
'purecode'          => false,
'version'           => '1.0.0',
'state'             => 'stable',
'privileges'        => Array(),
'class_definitions' => Array(),
'watches'           => Array(),
'package.xml' => Array
(  
    'license' => 'GPL',  
    'maintainers' => Array
    ( 
        'bergie' => Array
        (  
            'name' => 'Henri Bergius',  
            'email' => 'henri.bergius@iki.fi',  
            'role' => 'lead',  
        ),  
    ),
),

• name
  • Component name
• purecode
  • Defines whether the component is intended to be run on site or to be used as a library.
• version
  • Version of the component
• priviledges
  • Definition of possible component-specific ACL priviledges
• class_definitions
  • Definition of component MgdSchema classes
• watches
  • Registraition of possible object change watchers in the component
• package.xml
  • Directives used in component PEAR packaging