nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to compile tomcat for Jira installation in ubuntu

admin admin_trokdm

So, I'm mostly done installing Jira 8.0.2 on ubuntu server. But when I attempt to build tomcat;
$JIRA_INSTALLATION/bin/tomcat-native-1.2.18-src/native && ./configure --with-apr=/usr/local/apr/lib --with-java-home=/usr/lib/jvm/java-11-openjdk-amd64/bin/java

the below error is thrown;

checking for APR... configure: error: the --with-apr parameter is incorrect. It must specify an install prefix, a build directory, or an apr-config file.

I have been installing and re-installing apr all day, with no results, so any further information, or instructions, on this issue would be greatly appreciated.

Accepted answers

All comments

Nic Brough -Adaptavist-

This begs a simple question - why? Why are you building a Tomcat when the one bundled into the Atlassian distributions of Jira works (ok, it needs a couple of config tweaks if you choose to use apr, but nothing that needs a rebuild)

admin admin_trokdm

Because I was preparing to implement the server from tar.gz not from .bin

I have resolved this with the following;

cd "${INSTALL-DIR}"/bin && tar -zxvf tomcat-native.tar.gz
cd "${INSTALL_DIR}"/bin/tomcat-native-"${TOMCAT_VERSION}"-src/native && ./configure --with-apr=/usr --with-java-home="${JAVA_HOME}"
cd "${INSTALL_DIR}"/bin/tomcat-native-"${TOMCAT_VERSION}"-src/native && make && make install

admin admin_trokdm

There were a number of issues I experienced while delivering this server; from variations to previously validated scripting, to more surprisingly, a mislabeled package contained within the jira installation package which labeled the tomcat as an incorrect version; This was corrected rapidly once I discovered it.

Nic Brough -Adaptavist-

The .tar.gz install does not need compiling or building - you expand it and it's ready to run.

Where are the "variations" and "mislabeled packages" coming from? Is this a copy of another Jira some previous admin has been messing with?