关于EB Tresos中的plugin.xml文件的描述

1. Register the API in the corresponding extension point of the file plugin.xml.

2. The plugin.xml is an XML file used to register resources with EB tresos Studio.

3. EB tresos Studio supports multiple pre- configurations per module which are registered via the plugin.xml.

4. EB tresos Studio supports multiple recommended configurations per module which are registered via the plugin.xml.

5. In the plugin.xml, the software version, the specification version and the release version can be specified for each module.

6. If not changed in the plugin.xml the code generator searches the code templates within the plug-in underneath the directory generate.

7. To register a module transformer, the dreisoft.tresos.launcher2.api.plugin.moduletransformer extension point has to be registered in the new module's plugin.xml.

8. All code generators are marked as variant-aware in the plugin.xml: <parameter name="variantAware" value="true"/>

9. Open the plugin.xml of your plug-in and switch to the Extensions-tab

10. The ECU resource properties file must be registered at the extension point dreisoft.tresos.autosar2.api.plugin.ecuresource in the plugin.xml.

11. At each generator registration within the plugin.xml file, you can specify the tag canRunParallel to define whether the generator may run at the same time as other generators or not.

12. The EPC File Generator can be registered in the plugin.xml of the respective module via the generator extension-point

13. However, in the plugin manifest files (plugin.xml and Manifest.mf) no generated java methods for translation can be used.

14. In a plugin.xml no Java methods can be called to localize your plugin.

15. At last the NLS messages can be used in the plugin.xml.

16. To be able to show these DCtxt changes in the Results view, just register the ChangedDCtxtsResultWidget as resultGui parameter in the plugin.xml.

17. The common and recommended way is to register a push operations in the plugin.xml.

18. The common way to use triggers in the Sidebar view is to register them in the plugin.xml file.

19. Instead rather add a trigger in the plugin.xml, because there you can restrict the visibility of the trigger querying the current context.

20. You find the extension point description as a link in the plugin.xml editor.

21. To add a standalone editor or a dialog to the Sidebar view, add the following extension point to your plugin.xml: dreisoft.tresos.guidedconfig.api.plugin.trigger

22. To register an unattended wizard, add the following extension point to your plugin.xml: dreisoft.tresos.guidedconfig.api.plugin.trigger

23. This workflow description file must be registered either via an extension point in a plugin.xml or programmatically via the Workflows class.

24. It is possible to register a workflow via the dreisoft.tresos.workflow.api.plugin.workflow extention point in the plugin.xml of a module.

25. The plug-in just contains some workflow description files and registers the workflows in the plugin.xml.