|
From an email, this outlines our approach to supporting third-party application servers and databases Atlassian traditionally has a very loose definition of a 'supported environment'. We do not impose our appserver and database preferences on our users. In return we expect a level of understanding, that as a small company cannot be an expert in every third-party application. We 'support' anything that works, to the extent that our knowledge and time constraints permit. When it comes to new app servers like Geronimo and SJAS, or databases like Derby, we wait for evidence of interest from our user base. If anyone proves interested and persistent enough to get JIRA working, we pay our respects by investing some effort on our end, and if all goes well, that platform becomes 'supported'. This is not the CYA guarantee that big companies want. It means we will spend as much time helping as we reasonably can, in proportion to the platform's popularity. So our advice regarding new app servers and databases is as follows: If you are technically minded, enjoy a challenge and (most importantly) are able to switch platforms if things don't work out, we encourage you to try new things. Please report back of your experiences. Keep in mind that even just repackaging Tomcat, vendors can horribly break things (eg. JBoss 3's classloader), and that problems often arise in infrequently used parts of JIRA (upgrades, bulk operations, plugins, concurrent operations). If you just want something to work, we recommend sticking to what we know works. There are plenty of free, high quality app servers and databases available, and few reasons not to use them. |
On 'supported environments'
(None)