Installation using a self-built WAR file

The procedure is applicable when you decide to built a new WAR file using the JIRA WAR/EAR.

For this procedure, Kaamelot plugin 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

  • [atlassian-jira-enterprise-3.13.x]/edit-webapp/WEB-INF/lib
Perform the build of the WAR or EAR

Deploy the WAR/EAR

Follow the normal procedure to deploy the WAR/EAR on your J2EE Server.

1st Restart of JIRA

For this first Start of JIRA, you will have to follow the default Setup ...

During JIRA Setup (just after the first Setup Wizard page ), 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
Nothing else will done, the JIRA's Setup is not completed!

JIRA access is blocked. You are invited to Stop and Restart JIRA.

2nd Restart JIRA

When JIRA Restart, you will have to fill again the Setup (Nothing has been stored during 1st Start).

During the Setup, JIRA 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


In the same time, Minyaa's ConsistencyChecker will complete its installation. It :

  • tries to upgrade Kaamelot data. Here in this case, nothing should have been done.
JIRA and Minyaa are ready for use!