Documentation for JIRA 6.4. Not using this? See below:
(JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

Atlassian will stop releasing the WAR distribution of JIRA in JIRA 7.0.

What is the JIRA WAR distribution?

JIRA is available in two types of 'distributions':

Recommended distributions

WAR distribution

Require minimal setup

Requires manual configuration

Pre-packaged with the Apache Tomcat application server

Requires building and deployment to an existing application server installation

Include the JIRA Configuration Tool

Does not include the JIRA Configuration Tool

Recommended for all users

Suitable only for system administrators

(info) We recommend installing the 'recommended' distributions of JIRA over the WAR distribution — even for organisations with an existing application server environment.

(info) To install a recommended distribution of JIRA, see Installing JIRA.

Installing JIRA WAR

To install JIRA WAR, follow the instructions for your application server:

Additional Notes

 

2 Comments

  1. It's very disappointing to see that you're intending to drop support for the WAR version.

    We run a large number of internal WebApps and they are more resource-efficient, and more easily managed, from a single container.  If all WebApps insisted on their own custom environments, the additional resource and manual maintenance overhead would be extremely significant.

    We have already been putting off adopting FishEye because of this issue.

    I hope Atlassian reconsider the stance on this - what is the decision based on?

    1. I would also like to know why WAR packages seem to be being deprecated, not only by Atlassian, but many other companies producing Java web applications. I don't run bundled HTTP servers separately for each of dozens of regular sites, and it doesn't make sense to me to run entirely separate servers for every single Atlassian product, Nexus, and my own projects.