I've been trying to build JIRA 7.5.1 as a .war file to deploy as a web application in my j2ee container.
So I am following this.
However, I am running into several issues with the build.
It typically fails when trying to download/configure node/yarn.
I tried this...
to Edit jira-project\package.json - to exclude preinstall/postinstall
according to https://community.atlassian.com/t5/Jira-questions/JIRA-Software-
it got me further...
And I ran into this
[ERROR] error An unexpected error occurred: "https://npm-private.atlassian.io/@atlassian%2fstylelint-config-jira-fecq/-/@atlassian%2fstylelint-config-
jira-fecq-1.0.1.tgz: connect ETIMEDOUT 10.120.185.44:443".
[INFO] info If you think this is a bug, please open a bug report with the information provided in "c:\\Projects\\atlassian-jira-software-7.5.1-source\
Another post referred to this as a build issue on atlassian end that doesn't allow me to access npm-preivate.atlassion.io
Can you provide some direction here?
As an alternative.... I just need a jira .war file. If there is a way to do it without building from the source code. That may work too.
I understand you are wanting to deploy a WAR installation of Jira. That becomes much more difficult for Jira 7 versions since Atlassian officially discontinued all support for WAR installations back in 2016. We announced that this change back in 2014, (you can find the previous announcements on end of support announcements about this). That post explains why Atlassian stopped providing this as a means to deploy Jira. The short answer is that it makes installations much more difficult and in general provides a negative product experience.
That said there are Atlassian prepared WAR packages for Jira 6.4.x and before that you can still find in the Jira Downloads Archive. I am not sure if these older versions would suffice in your case or not.
I hope this helps,
I just found a related ticket to this problem in https://jira.atlassian.com/browse/JRASERVER-66224 It appears that this inability to build Jira from the current source is a bug.
I would recommend watching this bug ticket for updates to this.