Changes between Version 33 and Version 34 of PluginDevelopmentGuide
- Timestamp:
- 21.10.2016 11:44:25 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PluginDevelopmentGuide
v33 v34 49 49 50 50 === Begin a plugin project === 51 52 ==== Naming Conventions ==== 53 54 {{{ 55 When you are working with git, your new DeepaMehta repo should always start with 'dm4-', 56 eg. 'dm4-my-fancy-plugin'. The minor-version number is not part of the repo name. 57 58 But the Maven Artifact (jar file) should include the minor-version number, to display the 59 compatibility with a certain DeepaMehta release, eg. dm48-my-fancy-plugin-0.1.jar or 60 dm48-my-fancy-plugin-0.2-SNAPSHOT.jar . Usually a dm48- artefact needs adoption, to be 61 compatible with the next major version DeepaMehta 4.9. 62 }}} 63 51 64 52 65 From the developer's view a DeepaMehta plugin is just a directory on your hard disc. The directory can have an arbitrary name and exist at an arbitrary location. By convention the plugin directory begins with `dm4-` as it is aimed to the DeepaMehta 4 platform. The directory content adheres to a certain directory structure and file name conventions. The files are text files (xml, json, properties, java, js, css) and resources like images.