We run JIRA with Jetty 6.0.1 and MySQL 5.0.32 on Linux.

3.6.1 (Enterprise)

For 3.6.1, we use commons-pool 1.1, commons-dbcp 1.1, the connector for our version of MySQL, and JOTM 1.4.3. All of the jars can be placed in JIRA_HOME/edit-webapp/WEB-INF/lib. Note that these jars are not the latest versions of their respective libraries.

You can either add the carol.properties to JETTY_HOME/resources or generate a jar with just that file in it, added to the edit-webapp jars.

carol.properties:

carol.protocols=jrmp
carol.start.jndi=false
carol.start.ns=false
carol.start.rmi=false
carol.jvm.rmi.local.call=true
carol.jndi.java.naming.factory.url.pkgs=org.mortbay.naming

Finally, relevant changes we made to JIRA_HOME/edit-webapp/WEB-INF/classes/entityengine.xml:

    <transaction-factory class="org.ofbiz.core.entity.transaction.JotmFactory" />

    <datasource name="defaultDS" field-type-name="mysql"
      helper-class="org.ofbiz.core.entity.GenericHelperDAO"
      check-on-start="true"
      use-foreign-keys="false"
      use-foreign-key-indices="false"
      check-fks-on-start="false"
      check-fk-indices-on-start="false"
      add-missing-on-start="true"
      check-indices-on-start="true">
        <inline-jdbc jdbc-driver="com.mysql.jdbc.Driver"
                     jdbc-uri="jdbc:mysql://host/db" jdbc-username="user" jdbc-password="pass"
                     isolation-level="Serializable" />
    </datasource>

The actual JDBC connection information is specific to your installation. Once all of the files are in place, do ./build.sh compile (or, if you intend to generate a war, just ./build.sh) in JIRA_HOME. The working application will be in JIRA_HOME/tmp/build/war.

We prefer to allow anonymous users to see the Create new issue link, so in webapp/includes/decorators/bodytop.jsp, remove the permissions test starting at line 130 and its concluding bracket on line 141. Since creating a new issue with an anonymous user will by default warn about not having selected a project instead of not being logged in, we also changed webapp/includes/createissue-notloggedin.jsp by switching the if and elseIf statements around, so not being logged in takes precedence.

3.8.1 (Enterprise)

Stay tuned. We have not yet managed to make this work; it's not exactly a matter of copying over the 3.6.1 changes.