Installation on an already deployed JIRA

The procedure is applicable for JIRA with Standalone installation or for a Tomcat based installation.

For this procedure, Kaamelot should not have already installed. In other case, follow Installation with Import of XML Backup with Kaamelot Data.

Copy of Minyaa Files

You will have to copy Minyaa's JARs, its dependencies and a valid License Key file into the lib folder of the WEBApp.

  • [apache-tomcat-dir]/webapps/jira/WEB-INF/lib
  • [atlassian-jira-enterprise-3.13.x-standalone]/atlassian-jira/WEB-INF/lib

1st Restart of JIRA

During JIRA Restart, Minyaa's ConsistencyChecker :
  • performs an auto-register of the deployed License Key file
  • applies some required changes in JIRA settings (Entity Model, Velocity property and JSP upgrade
  • tries to upgrade Kaamelot data. Here in this case, nothing should have been done.
  • blocks JIRA access when the installation is done. You are invited to Stop and Restart JIRA.

2nd Restart of JIRA

When JIRA Restart,
  • JIRA DatabaseUtil discovers the changes in the Entity Model and applies them to the Database 
    2009-07-13 11:22:52,937 main [core.entity.jdbc.DatabaseUtil] Entity "LinkEntity" has no table in the database
2009-07-13 11:22:52,937 main [core.entity.jdbc.DatabaseUtil] Entity "LinkScheme" has no table in the database
2009-07-13 11:22:52,953 main [core.entity.jdbc.DatabaseUtil] Entity "WorklogExt" has no table in the database
2009-07-13 11:22:52,953 main [core.entity.jdbc.DatabaseUtil] Entity "WorklogType" has no table in the database


  • Minyaa ConsistencyCheckerService will run each UpgradeManager found in each Minyaa Plugins

    2009-08-26 15:50:25,328 JiraQuartzScheduler_Worker-2 WARN [atlassian.jira.service.ConsistencyCheckerService] Start UpgradeManager [com.minyaa.upgrade.MinyaaCoreUpgradeManager] for Plugin [jira.plugin.minyaa.core]
2009-08-26 15:50:25,328 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Detected that an upgrade is needed; existing data at build 0
2009-08-26 15:50:25,328 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Doing Upgrade...
2009-08-26 15:50:25,328 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Performing Upgrade Task: Upgrades Kaamelot's Portlets to Minyaa's Portlets
2009-08-26 15:50:25,328 JiraQuartzScheduler_Worker-2 ERROR [minyaa.upgrade.tasks.MinyaaCoreUpgradeTask_001] Portlet [INTRODUCTION] has no known mapping ...
2009-08-26 15:50:25,515 JiraQuartzScheduler_Worker-2 ERROR [minyaa.upgrade.tasks.MinyaaCoreUpgradeTask_001] Portlet [PROJECTS] has no known mapping ...
2009-08-26 15:50:25,515 JiraQuartzScheduler_Worker-2 ERROR [minyaa.upgrade.tasks.MinyaaCoreUpgradeTask_001] Portlet [SAVEDFILTERS] has no known mapping ...
2009-08-26 15:50:25,515 JiraQuartzScheduler_Worker-2 ERROR [minyaa.upgrade.tasks.MinyaaCoreUpgradeTask_001] Portlet [ASSIGNEDTOME] has no known mapping ...
2009-08-26 15:50:25,515 JiraQuartzScheduler_Worker-2 ERROR [minyaa.upgrade.tasks.MinyaaCoreUpgradeTask_001] Portlet [INPROGRESS] has no known mapping ...
2009-08-26 15:50:25,515 JiraQuartzScheduler_Worker-2 ERROR [minyaa.upgrade.tasks.MinyaaCoreUpgradeTask_001] Portlet [USERISSUES] has no known mapping ...
2009-08-26 15:50:25,531 JiraQuartzScheduler_Worker-2 ERROR [minyaa.upgrade.tasks.MinyaaCoreUpgradeTask_001] Portlet [ADMIN] has no known mapping ...
2009-08-26 15:50:25,531 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade Task: 'Upgrades Kaamelot's Portlets to Minyaa's Portlets' succeeded
2009-08-26 15:50:25,531 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Setting current build number on to 1
2009-08-26 15:50:25,546 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Performing Upgrade Task: Analyses all Workflows to identify required changes ...
2009-08-26 15:50:25,546 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade Task: 'Analyses all Workflows to identify required changes ...' succeeded
2009-08-26 15:50:25,546 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Setting current build number on to 2
2009-08-26 15:50:25,562 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Performing Upgrade Task: Migrates Kaamelot's CustomFields to Minyaa's CustomFields
2009-08-26 15:50:25,578 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade Task: 'Migrates Kaamelot's CustomFields to Minyaa's CustomFields' succeeded
2009-08-26 15:50:25,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Setting current build number on to 3
2009-08-26 15:50:25,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Performing Upgrade Task: Upgrades Kaamelot Roll Over Backup Service
2009-08-26 15:50:25,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade Task: 'Upgrades Kaamelot Roll Over Backup Service' succeeded
2009-08-26 15:50:25,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Setting current build number on to 4
2009-08-26 15:50:25,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade succeeded! Setting data build number to 4
2009-08-26 15:50:25,593 JiraQuartzScheduler_Worker-2 WARN [atlassian.jira.util.LuceneUtils] Directory C:\temp\demo\Minyaa-3.13.5.1.1\files\indexes/entities/searchrequest does not exist - perhaps it was deleted?  Creating..
2009-08-26 15:50:26,593 JiraQuartzScheduler_Worker-2 WARN [atlassian.jira.service.ConsistencyCheckerService] No UpgradeManager for Plugin [jira.plugin.minyaa.tools]
2009-08-26 15:50:26,593 JiraQuartzScheduler_Worker-2 WARN [atlassian.jira.service.ConsistencyCheckerService] Start UpgradeManager [com.minyaa.upgrade.MinyaaTimeUpgradeManager] for Plugin [jira.plugin.minyaa.time]
2009-08-26 15:50:26,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Detected that an upgrade is needed; existing data at build 0
2009-08-26 15:50:26,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Doing Upgrade...
2009-08-26 15:50:26,593 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Performing Upgrade Task: Upgrades Relation between Worker/Issue
2009-08-26 15:50:26,593 JiraQuartzScheduler_Worker-2 WARN [minyaa.upgrade.tasks.MinyaaTimeUpgradeTask_001] Updating Issue/Worker Relations
2009-08-26 15:50:26,609 JiraQuartzScheduler_Worker-2 WARN [minyaa.upgrade.tasks.MinyaaTimeUpgradeTask_001] Starting to update Issue/Worker Relations for [admin]
2009-08-26 15:50:26,609 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade Task: 'Upgrades Relation between Worker/Issue' succeeded
2009-08-26 15:50:26,609 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Setting current build number on to 1
2009-08-26 15:50:26,609 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Performing Upgrade Task: Migrates Worker CustomField to CurrentWorker CustomField
2009-08-26 15:50:26,625 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade Task: 'Migrates Worker CustomField to CurrentWorker CustomField' succeeded
2009-08-26 15:50:26,625 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Setting current build number on to 2
2009-08-26 15:50:26,625 JiraQuartzScheduler_Worker-2 INFO [atlassian.jira.upgrade.AbstractPluginUpgradeManager] Upgrade succeeded! Setting data build number to 2
2009-08-26 15:50:26,937 JiraQuartzScheduler_Worker-2 WARN [atlassian.jira.service.ConsistencyCheckerService] No UpgradeManager for Plugin [jira.plugin.minyaa.workflows]
2009-08-26 15:50:26,937 JiraQuartzScheduler_Worker-2 WARN [atlassian.jira.service.ConsistencyCheckerService] No UpgradeManager for Plugin [jira.plugin.minyaa.projects]
2009-08-26 15:50:26,937 JiraQuartzScheduler_Worker-2 WARN [atlassian.jira.service.ConsistencyCheckerService] No UpgradeManager for Plugin [jira.plugin.minyaa.spread]


JIRA and Minyaa are ready for use!

Installation on Stanalone JIRA from Scratch

The procedure will be the same than above procedure excepted that a Tomncat Stop and Restart will be required after 2nd Restart of JIRA step, because PluginUpgradeManager are not launched during a JIRA Setup.

See Demonstration.