Feature #2338
Mis à jour par Matthieu Decorde il y a plus de 7 ans
h3. plugin.xml
Plugins configuration in plugin.xml files and co can be tricky. E.G. a class name changed, editor ID changed...
Tests to implement :
* in Overview tab
** Execution Environment is JavaSE-1.6 (for now)
** this plug-in is a singleton is checked
** ID is the project name
* in runtime tab
** all packages are exported
* in extension points tab
** schema path must exists
** extension point ID must be the full classname of the Extension class
* in extensions tab
** all extension point ID must exists
** check there is no "id" clash per extension type (ex: 2 separators with same id)
* in "build configuration" tab
** the "icons" directory is added to the binary
** the "OSGI-INF" directory is added to the binary
h3. feature.xml
* all included plugin must be optionals (to allow update by another feature) plugin)
Plugins configuration in plugin.xml files and co can be tricky. E.G. a class name changed, editor ID changed...
Tests to implement :
* in Overview tab
** Execution Environment is JavaSE-1.6 (for now)
** this plug-in is a singleton is checked
** ID is the project name
* in runtime tab
** all packages are exported
* in extension points tab
** schema path must exists
** extension point ID must be the full classname of the Extension class
* in extensions tab
** all extension point ID must exists
** check there is no "id" clash per extension type (ex: 2 separators with same id)
* in "build configuration" tab
** the "icons" directory is added to the binary
** the "OSGI-INF" directory is added to the binary
h3. feature.xml
* all included plugin must be optionals (to allow update by another feature) plugin)