Add Ons/Plugin around Atlassian products can be :
These plugins are the more current and contains :
|
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. |
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 :
|
Most of Alkaes plugins are now provided as OBR files, as soon as they have a dependency (License Management, Settings Management, ...).
The Alkaes Minyaa Suite provides different plugins :
As today, Minyaa Plugins are provided in the Atlassian Marketplace through :
In future, all others will be also available
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 :
On this page: |
See also ... |