You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Plugin Types

Add Ons/Plugin around Atlassian products can be :

  • Simple JAR files
  • Or OBR Files

Plugins provided as JAR Files

These plugins are the more current and contains :

  • The classes and resources issued from the Java project
  • But also some classes and resources issued from their dependencies, if they are not marked as provided by the Application.

Plugins provided as OBR Files

 

These plugins are provided when a plugin has other plugins in dependencies, and it is able to provide them.

On installation, JIRA will deploy the plugin B (jar) and also the plugin C and D if they are not already installed or with older versions.

Plugin's Hierarchy

When a plugin is provided, it may come with different dependencies.

If these dependencies are embedded, the plugin will be provided as a OBR file, else it will be provided as a JAR file.

With the current example, we can imagine all combination :

  • Plugin A with B, C & D embedded,
  • Plugin A with B,C embedded, Plugin D alone
    • Plugin D will have to be deployed before the deployment of the Plugin A
  • Plugin A with B embedded, Plugin C & D alone
    • Plugin C & D will have to be deployed before the deployment of the Plugin A
  • Plugin A with Plugin D embedded, Plugin B with D & C embedded
    • Plugin B will have to be deployed before the Plugin A
    • On Plugin A deployment, the Plugin D will be not deployed since it is already provided by the Plugin B, excepted if it version is higher

 

Alkaes Plugins

Most of Alkaes plugins are now provided as OBR files, as soon as they have a dependency (License Management, Settings Management, ...).

Different distributions

The Alkaes Minyaa Suite provides different plugins :

  • Feature Plugins (commercial) : Core, Workflows, Time, Users, Reports Spread
  • Feature Plugins (not commercialized alone) : Project Factory, Alkaes Index Forced
  • Technical Plugins : License Management, Settings Managements, Common

Licenses Hierarchy

Due to such dependency hierarchy, Alkaes plugins may embed plugins are also controlled by License. 

To resolve this, their License Management is able to extend a license to the dependencies.

By example Minyaa Time has a dependency with Minyaa Core, and then its License allows also the usage of MInyaa Core.

In the same way, Minyaa Suite is not a Feature Plugin. It is just a way to aggregate all plugins of the Suite. And following the same mechanism, Licenses for Minyaa Suite is able to allow the usage of all the hierarchy of Plugin.

With Minyaa 3.x, Minyaa Suite lIcenses were provided for Trial purposes and also as soon as you was licensed for 2 or more plugins.

Since Minyaa 4.x, Minyaa Suite licenses are provided only for Trial purposes. When you purchase some plugins, you receive a license of each of them.

By example :

  • You deploy Minyaa Suite and evaluate it with a Trial License 
  • You decide to purchase Minyaa Time and Minyaa Workflows
  • You will then receive 2 license keys for each of them
  • You will have to apply the license of each of them
  • Others plugins that were licensed by the Trial License on Minyaa Suite, will be no more usable as soon as the Trial license will expired.
  • To avoid some side effect, it will be better to uninstall Minyaa Suite plugin and other not licensed plugins (Users, Reports & Spread). Note that Core will be licensed by inheritance of Minyaa Time which has a dependency on it.

 

On this page:

 

Useful hint

See also ...

  • No labels

Alkaes Consulting