JIRA Software Source 7.4.2. Fails To Build Due To Yarn Install

Hi

I'm trying to rebuild the JIRA Software 7.4.2. source (on a Windows 7 PC) so I can modify some plugins.

However when I run build I get the following error

[INFO] Atlassian JIRA - Testing - Cache Check Tests ....... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 41.486 s
[INFO] Finished at: 2017-08-23T12:47:47+01:00
[INFO] Final Memory: 87M/532M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.3:yarn (yarn install) on project jira-project: Failed to run task: 'yarn install -pure-lockfile --prefer-offline' failed. (error code 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

 

Does anyone have an idea of how I can fix or debug this issue?

6 answers

1 vote

Hello

I have had similar problems.  

I solved the issue your running into be installing node.js locally changing the jira-project/package.json file to the following

"preinstall": "node ./conf/frontend/npm/preinstall.js",
"postinstall": "node ./conf/frontend/npm/postinstall.js",

This worked for me.

I would also suggest removing the devDependencies of 

"@atlassian/eslint-config-jira-fecq": "^3",
"@atlassian/fecq-enforcer": ">=5.1.2",
"@atlassian/stylelint-config-jira-fecq": "^1",

As these will give you errors.  see https://community.developer.atlassian.com/t/error-building-atlassian-jira-7-4-0/7563 for details.

Neil

Thanks Neil, that does indeed fix my Node.js issue.

I'm still having the yarn install problem, which it looks like you are from the link you posted.

Annoying that this is still present in the 7.4.2 source as well.

I removed the preinstall and postinstall lines and the source is now building, it's obviously taking some time but it's got a lot further than it has before

Hi Neil/Dalectric,

I am building 7.5.1 source, as suggested in your previous comments, I removed the devDependencies and also modified the preinstall and postinstall from package.json file but I am getting the below error. Could you please suggest on this issue?

[ERROR] 'npm' is not recognized as an internal or external command,
[ERROR] operable program or batch file.
[ERROR] child_process.js:631
[ERROR]     throw err;
[ERROR]     ^
[ERROR]
[ERROR] Error: Command failed: npm config get @atlassian:registry
[ERROR] 'npm' is not recognized as an internal or external command,
[ERROR]
[ERROR] operable program or batch file.
[ERROR]
[ERROR]
[ERROR]     at checkExecSyncError (child_process.js:588:13)
[ERROR]     at Object.execSync (child_process.js:628:13)
[ERROR]     at Object.<anonymous> (c:\atlassian-jira-software-7.5.1-source\jira-project\conf\frontend\npm\preinstall.js:2:34)
[ERROR]     at Module._compile (module.js:569:30)
[ERROR]     at Object.Module._extensions..js (module.js:580:10)
[ERROR]     at Module.load (module.js:503:32)
[ERROR]     at tryModuleLoad (module.js:466:12)
[INFO] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[ERROR]     at Function.Module._load (module.js:458:3)
[ERROR]     at Function.Module.runMain (module.js:605:10)
[ERROR]     at startup (bootstrap_node.js:158:16)
[ERROR] error Command failed with exit code 1.
[DEBUG] Skipping artifactory staging as maven build fails

 

Hi Niel,

I installed node.js and the error was resolved however I got a new error.

null
Found Banned Dependency: com.atlassian.browsers:atlassian-browsers-windows:jar:2.7.0-m1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute(AbstractBanDependencies.java:112)
at com.atlassian.maven.enforcer.BanVersionDeps.execute(BanVersionDeps.java:81)
at org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:193)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[WARNING] Rule 2: com.atlassian.maven.enforcer.BanVersionDeps failed with message:
null
Found Banned Dependency: com.atlassian.browsers:atlassian-browsers-windows:jar:2.7.0-m1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
[DEBUG] Skipping artifactory staging as maven build fails
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Atlassian JIRA ..................................... SUCCESS [ 26.883 s]
[INFO] Atlassian JIRA - Code - Components ................. SUCCESS [ 0.477 s]
[INFO] jira-lucene-cutdown ................................ SUCCESS [ 1.842 s]
[INFO] Atlassian JIRA - Code - API ........................ SUCCESS [ 32.627 s]
[INFO] Atlassian JIRA - Code - DMZ API .................... SUCCESS [ 2.980 s]
[INFO] Atlassian JIRA - Code - Lucene DMZ ................. SUCCESS [ 3.761 s]
[INFO] Atlassian JIRA - Code - Core ....................... SUCCESS [02:04 min]
[INFO] Atlassian JIRA - Plugins ........................... SUCCESS [ 2.004 s]
[INFO] Atlassian JIRA - Language Packs .................... SUCCESS [ 3.451 s]
[INFO] Atlassian JIRA - Code - Parent for unit tests ...... SUCCESS [ 0.427 s]
[INFO] Atlassian JIRA - Code - Common Unit Tests .......... SUCCESS [ 15.569 s]
[INFO] Atlassian JIRA - Code - Test License Helper ........ SUCCESS [ 1.703 s]
[INFO] Atlassian JIRA - JIRA Configuration Tool ........... SUCCESS [ 9.860 s]
[INFO] Atlassian JIRA - Code - Unit Tests ................. SUCCESS [ 8.370 s]
[INFO] Atlassian JIRA - Code - Unit Database Tests ........ SUCCESS [ 9.729 s]
[INFO] Atlassian JIRA - Plugins - ActiveObjects SPI ....... SUCCESS [ 35.436 s]
[INFO] Atlassian JIRA - Plugins - OAuth Service Provider SPI SUCCESS [ 35.381 s]
[INFO] Atlassian JIRA - Plugins - OAuth Consumer SPI ...... SUCCESS [ 36.182 s]
[INFO] Atlassian JIRA - Plugins - REST .................... SUCCESS [ 1.937 s]
[INFO] Atlassian JIRA - Plugins - REST Plugin API ......... SUCCESS [ 4.229 s]
[INFO] Atlassian JIRA - Plugins - REST Plugin ............. SUCCESS [02:52 min]
[INFO] Atlassian JIRA - Plugins - Gadgets Plugin .......... SUCCESS [ 28.746 s]
[INFO] Atlassian JIRA - Plugins - SAL Plugin .............. SUCCESS [ 36.826 s]
[INFO] Atlassian JIRA - Plugins - WebHooks Plugin ......... SUCCESS [ 16.075 s]
[INFO] Atlassian JIRA - Testing - Func Tests Parent ....... SUCCESS [ 0.414 s]
[INFO] Atlassian JIRA - Testing - Func Tests .............. SUCCESS [01:01 min]
[INFO] Atlassian JIRA - Testing - UI Test Utils ........... SUCCESS [ 5.653 s]
[INFO] Atlassian JIRA - Testing - Page Objects Library .... FAILURE [ 1.330 s]

Hi,

Yes I had the same issue.  You need to update the dependencies for page objects to point to 2.8.1 not the 2.7.0-m1 that comes with the download.  After the error message of [INFO] Atlassian JIRA - Testing - Page Objects Library .... FAILURE [ 1.330 s]  there should be a continuation of the error message that will point to the file that caused the error message.

I'll search my build to see if I can find it.  If you have it post the error and I'll look it up.

Neil 

Are you looking for this error?

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-versions) on project atlassian-jira-pageobjects: Some Enforcer rules have failed. Look above for specific messages expl
aining why the rule failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-versions) on project atlassian-jira-pageobjects: Some Enforcer rules ha
ve failed. Look above for specific messages explaining why the rule failed.
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
        at org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:237)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 19 more

Hi Neil,

You suggested to update the dependencies for page objects to point to 2.8.1 not the 2.7.0-m1. Could you please let me know which files I need to update?

Some more info after running with -X option for mvn

[INFO] Installed node locally.
[INFO] Installing Yarn version v0.21.3
[DEBUG] Creating install directory E:\JIRA_7.4.2_Source\jira-project\target\node\yarn
[INFO] Unpacking E:\JIRA_7.4.2_Source\localrepo\com\github\eirslett\yarn\0.21.3\yarn-0.21.3.\yarn-v0.21.3.tar.gz into E:\JIRA_7.4.2_Source\jira-project\target\node\yarn
[INFO] Installed Yarn locally.
[INFO]
[INFO] --- frontend-maven-plugin:1.3:yarn (yarn install) @ jira-project ---
[DEBUG] Configuring mojo com.github.eirslett:frontend-maven-plugin:1.3:yarn from plugin realm ClassRealm[plugin>com.github.eirslett:frontend-maven-plugin:1.3, parent: sun.misc.Launcher$AppClassLoader@4e25154f]
[DEBUG] Configuring mojo 'com.github.eirslett:frontend-maven-plugin:1.3:yarn' with basic configurator -->
[DEBUG] (f) arguments = install --pure-lockfile --prefer-offline
[DEBUG] (f) environmentVariables = {FRONTEND_DIST_MODE=false}
[DEBUG] (f) installDirectory = E:\JIRA_7.4.2_Source\jira-project\target
[DEBUG] (f) project = MavenProject: com.atlassian.jira:jira-project:7.4.2 @ E:\JIRA_7.4.2_Source\jira-project\pom.xml
[DEBUG] (f) repositorySystemSession = org.eclipse.aether.DefaultRepositorySystemSession@5cbe72b9
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@2248d140
[DEBUG] (f) skip = false
[DEBUG] (f) skipTests = false
[DEBUG] (f) workingDirectory = E:\JIRA_7.4.2_Source\jira-project
[DEBUG] (f) yarnInheritsProxyConfigFromMaven = true
[DEBUG] (f) execution = com.github.eirslett:frontend-maven-plugin:1.3:yarn {execution: yarn install}
[DEBUG] -- end configuration --
[INFO] Running 'yarn install --pure-lockfile --prefer-offline' in E:\JIRA_7.4.2_Source\jira-project
[INFO] yarn install v0.21.3
[INFO] $ ./conf/frontend/node ./conf/frontend/npm/preinstall.js
[ERROR] '.\conf\frontend\node' is not recognized as an internal or external command,
[ERROR] operable program or batch file.
[ERROR] error Command failed with exit code 1.
[INFO] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[ERROR] openssl config failed: error:02001003:system library:fopen:No such process

I've fixed the node issue by copying node.exe from 

\jira-project\target\node

to 

\jira-project\conf\frontend

However I now get another error which doesn't seem so simple to fix

[INFO] Installed node locally.
[INFO] Installing Yarn version v0.21.3
[INFO] Unpacking E:\JIRA_7.4.2_Source\localrepo\com\github\eirslett\yarn\0.21.3\yarn-0.21.3.\yarn-v0.21.3.tar.gz into E:\JIRA_7.4.2_Source\jira-project\target\node\yarn
[INFO] Installed Yarn locally.
[INFO]
[INFO] --- frontend-maven-plugin:1.3:yarn (yarn install) @ jira-project ---
[INFO] Running 'yarn install --pure-lockfile --prefer-offline' in E:\JIRA_7.4.2_Source\jira-project
[INFO] yarn install v0.21.3
[INFO] $ ./conf/frontend/node ./conf/frontend/npm/preinstall.js
[ERROR] 'npm' is not recognized as an internal or external command,
[ERROR] operable program or batch file.
[ERROR] child_process.js:532
[ERROR] throw err;
[ERROR] ^
[ERROR]
[ERROR] Error: Command failed: npm config get @atlassian:registry
[ERROR] 'npm' is not recognized as an internal or external command,
[ERROR]
[ERROR] operable program or batch file.

Hi 

If you manage to get the build to work let me know.

I've worked through a number of issues with the pom files and missing dependancy and wrong paths.   If you get any other errors I may have come across them. 

Currently I'm stuck on the following in the HA Container tests.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:copy (copy-jira-war-and-dependencies) on project ha-container-tests: Unable to find artifact. Could not find artifact com.atlassian.jira:jira-webapp-dist:war:7.4.2 in atlassian-proxy (https://packages.atlassian.com/maven/repository/public)
[ERROR]
[ERROR] Try downloading the file manually from the project website.

The file doesn't exit in the repositry listed. 

Neil

Thanks, the build doesn't work still for me, but it's progressing I think.

I've changed to 7.4.4. source.

I've carried out the same changes and am getting stuck at the following

[WARNING] Rule 3: com.atlassian.maven.enforcer.BanVersionDeps failed with messag
e:

...

null
Found Banned Dependency: com.atlassian.browsers:atlassian-browsers-windows:jar:2
.7.0-m1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
[INFO] ------------------------------------------------------------------------

...

[INFO] Atlassian JIRA - Testing - UI Test Utils ........... SUCCESS [ 1.910 s]
[INFO] Atlassian JIRA - Testing - Page Objects Library .... FAILURE [04:26 min]
[INFO] Atlassian JIRA - Plugins - Feedback Plugin ......... SKIPPED

It'd be great if you have any tips on how to fix that. I'll continue to plug away at it.

I've given up with trying to get the source to build, I just don't have the time to get it to work. 

I've managed to get the imporant plugin I modified building so I'll stick with that.

Thanks for your help with this and good luck getting it to build.

0 vote

Hi all,

Sorry to hear about these problems.  However I believe this is a documented bug in Jira.  Please see https://jira.atlassian.com/browse/JRASERVER-66224 for more details.  

Once a fix for this exists, that bug page will be updated with a solution to this.  I would recommend watching this bug page for updates.

Regards,
Andy

Hi Andrew,

After we installed the node.js and updated the preinstall and postinstall from package.json file the build went thru the npm issue but I got a new error. Is the below error also related to the bug you mentioned?

null
Found Banned Dependency: com.atlassian.browsers:atlassian-browsers-windows:jar:2.7.0-m1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
        at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute(AbstractBanDependencies.java:112)
        at com.atlassian.maven.enforcer.BanVersionDeps.execute(BanVersionDeps.java:81)
        at org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:193)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[WARNING] Rule 2: com.atlassian.maven.enforcer.BanVersionDeps failed with message:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Atlassian JIRA ..................................... SUCCESS [ 26.883 s]
[INFO] Atlassian JIRA - Code - Components ................. SUCCESS [  0.477 s]
[INFO] jira-lucene-cutdown ................................ SUCCESS [  1.842 s]
[INFO] Atlassian JIRA - Code - API ........................ SUCCESS [ 32.627 s]
[INFO] Atlassian JIRA - Code - DMZ API .................... SUCCESS [  2.980 s]
[INFO] Atlassian JIRA - Code - Lucene DMZ ................. SUCCESS [  3.761 s]
[INFO] Atlassian JIRA - Code - Core ....................... SUCCESS [02:04 min]
[INFO] Atlassian JIRA - Plugins ........................... SUCCESS [  2.004 s]
[INFO] Atlassian JIRA - Language Packs .................... SUCCESS [  3.451 s]
[INFO] Atlassian JIRA - Code - Parent for unit tests ...... SUCCESS [  0.427 s]
[INFO] Atlassian JIRA - Code - Common Unit Tests .......... SUCCESS [ 15.569 s]
[INFO] Atlassian JIRA - Code - Test License Helper ........ SUCCESS [  1.703 s]
[INFO] Atlassian JIRA - JIRA Configuration Tool ........... SUCCESS [  9.860 s]
[INFO] Atlassian JIRA - Code - Unit Tests ................. SUCCESS [  8.370 s]
[INFO] Atlassian JIRA - Code - Unit Database Tests ........ SUCCESS [  9.729 s]
[INFO] Atlassian JIRA - Plugins - ActiveObjects SPI ....... SUCCESS [ 35.436 s]
[INFO] Atlassian JIRA - Plugins - OAuth Service Provider SPI SUCCESS [ 35.381 s]
[INFO] Atlassian JIRA - Plugins - OAuth Consumer SPI ...... SUCCESS [ 36.182 s]
[INFO] Atlassian JIRA - Plugins - REST .................... SUCCESS [  1.937 s]
[INFO] Atlassian JIRA - Plugins - REST Plugin API ......... SUCCESS [  4.229 s]
[INFO] Atlassian JIRA - Plugins - REST Plugin ............. SUCCESS [02:52 min]
[INFO] Atlassian JIRA - Plugins - Gadgets Plugin .......... SUCCESS [ 28.746 s]
[INFO] Atlassian JIRA - Plugins - SAL Plugin .............. SUCCESS [ 36.826 s]
[INFO] Atlassian JIRA - Plugins - WebHooks Plugin ......... SUCCESS [ 16.075 s]
[INFO] Atlassian JIRA - Testing - Func Tests Parent ....... SUCCESS [  0.414 s]
[INFO] Atlassian JIRA - Testing - Func Tests .............. SUCCESS [01:01 min]
[INFO] Atlassian JIRA - Testing - UI Test Utils ........... SUCCESS [  5.653 s]
[INFO] Atlassian JIRA - Testing - Page Objects Library .... FAILURE [  1.330 s]

Yes, I believe this is still related to the bug I posted above.  Since there is a specific package that does not appear to be publicly available, it looks like either this is going to need to be made public or a new set of steps would be required to be able to build Jira from source in these versions of 7.4.0 and higher of Jira.

To the best of my knowledge Jira 7.2.0  through 7.3.8 do not have this specific problem when being built from source code because they do not utilize this new code package.

Hi Andrew,

I tried to build 7.3.5 but I got the Jira-jars-tomcat-distribution.zip dependency missed error. I checked in atlassian public maven repo for Jira-jars-tomcat-distribution.zip file but it is not available. Could you please suggest if there is any way I could get this file in order to continue the build?

[INFO] Reactor Summary:
[INFO]
[INFO] Atlassian JIRA ..................................... SUCCESS [  1.282 s]
[INFO] Atlassian JIRA - Code - Components ................. SUCCESS [  0.104 s]
[INFO] jira-lucene-cutdown ................................ SUCCESS [  1.198 s]
[INFO] Atlassian JIRA - Code - API ........................ SUCCESS [ 29.107 s]
[INFO] Atlassian JIRA - Code - Lucene DMZ ................. SUCCESS [  1.180 s]
[INFO] Atlassian JIRA - Code - Core ....................... SUCCESS [03:09 min]
[INFO] Atlassian JIRA - Plugins ........................... SUCCESS [  2.818 s]
[INFO] Atlassian JIRA - Language Packs .................... SUCCESS [  0.825 s]
[INFO] Atlassian JIRA - Code - Parent for unit tests ...... SUCCESS [  0.073 s]
[INFO] Atlassian JIRA - Code - Common Unit Tests .......... SUCCESS [ 10.502 s]
[INFO] Atlassian JIRA - Code - Test License Helper ........ SUCCESS [  0.860 s]
[INFO] Atlassian JIRA - JIRA Configuration Tool ........... SUCCESS [  4.190 s]
[INFO] Atlassian JIRA - Code - Unit Tests ................. SUCCESS [ 10.859 s]
[INFO] Atlassian JIRA - Code - Unit Database Tests ........ SUCCESS [  3.902 s]
[INFO] Atlassian JIRA - Plugins - ActiveObjects SPI ....... SUCCESS [  8.069 s]
[INFO] Atlassian JIRA - Plugins - OAuth Service Provider SPI SUCCESS [  6.244 s]
[INFO] Atlassian JIRA - Plugins - OAuth Consumer SPI ...... SUCCESS [  8.251 s]
[INFO] Atlassian JIRA - Plugins - REST .................... SUCCESS [  0.236 s]
[INFO] Atlassian JIRA - Plugins - REST Plugin API ......... SUCCESS [  7.950 s]
[INFO] Atlassian JIRA - Plugins - REST Plugin ............. SUCCESS [02:36 min]
[INFO] Atlassian JIRA - Plugins - Gadgets Plugin .......... SUCCESS [ 37.877 s]
[INFO] Atlassian JIRA - Plugins - SAL Plugin .............. SUCCESS [  8.323 s]
[INFO] Atlassian JIRA - Testing - Func Tests Parent ....... SUCCESS [  0.095 s]
[INFO] Atlassian JIRA - Testing - Func Tests .............. SUCCESS [01:17 min]
[INFO] Atlassian JIRA - Testing - UI Test Utils ........... SUCCESS [  1.242 s]
[INFO] Atlassian JIRA - Testing - Page Objects Library .... SUCCESS [01:31 min]
[INFO] Atlassian JIRA - Plugins - Feedback Plugin ......... SUCCESS [  2.202 s]
[INFO] Atlassian JIRA - Testing - WebDriver Tests ......... SUCCESS [01:23 min]
[INFO] Atlassian JIRA - Plugins - Project Config Plugin ... SUCCESS [ 53.715 s]
[INFO] Atlassian JIRA - Plugins - Application Properties .. SUCCESS [  3.052 s]
[INFO] Atlassian JIRA - Plugins - Admin Navigation Component SUCCESS [  3.836 s]
[INFO] Atlassian JIRA - Plugins - Closure Template Renderer SUCCESS [  5.946 s]
[INFO] Atlassian JIRA - Plugins - View Issue Panels ....... SUCCESS [  7.372 s]
[INFO] Atlassian JIRA - Plugins - Look And Feel Logo Upload Plugin SUCCESS [  5.764 s]
[INFO] Atlassian JIRA - Plugins - Header Plugin ........... SUCCESS [  7.716 s]
[INFO] Atlassian JIRA - Plugins - My JIRA Home ............ SUCCESS [  5.270 s]
[INFO] Atlassian JIRA - Plugins - Onboarding .............. SUCCESS [  7.480 s]
[INFO] Atlassian JIRA - Plugins - Share Content Component . SUCCESS [  2.422 s]
[INFO] Atlassian JIRA - Plugins - LESS integration ........ SUCCESS [  6.038 s]
[INFO] Atlassian JIRA - Plugins - Analytics whitelist ..... SUCCESS [  0.457 s]
[INFO] Atlassian JIRA - Plugins - Common AppLinks Based Issue Link Plugin SUCCESS [  6.437 s]
[INFO] Atlassian JIRA - Plugins - Remote JIRA Link ........ SUCCESS [  5.140 s]
[INFO] Atlassian JIRA - Plugins - Issue Web Link .......... SUCCESS [  1.876 s]
[INFO] Atlassian JIRA - Plugins - Confluence Link ......... SUCCESS [  5.782 s]
[INFO] Atlassian JIRA - Plugins - WebHooks Plugin ......... SUCCESS [  9.319 s]
[INFO] Atlassian JIRA - Plugins - Post setup announcements plugin SUCCESS [  4.914 s]
[INFO] Atlassian JIRA - Plugins - Core Reports ............ SUCCESS [  6.493 s]
[INFO] Atlassian JIRA - Plugins - Admin Upgrades .......... SUCCESS [  6.126 s]
[INFO] Atlassian JIRA - Plugins - Bundled Plugins ......... SUCCESS [02:14 min]
[INFO] Atlassian JIRA - Webapp ............................ SUCCESS [03:56 min]
[INFO] Atlassian JIRA - Plugins - Plugin Test Resources ... SUCCESS [  8.947 s]
[INFO] Atlassian JIRA - Plugins - DevMode - Func Test Plugin SUCCESS [ 13.904 s]
[INFO] Atlassian JIRA - Plugins - Development Only - Reference Plugin SUCCESS [ 10.023 s]
[INFO] Atlassian JIRA - Plugins - Reference Dependent Plugin SUCCESS [  4.659 s]
[INFO] Atlassian JIRA - Plugins - Development Only - Reference Upgraded Plugin SUCCESS [ 17.801 s]
[INFO] Atlassian JIRA - Plugins - Development Only - Reference Language Pack SUCCESS [  3.985 s]
[INFO] Atlassian JIRA - Plugins - Development Only - Reference Language Pack SUCCESS [  4.773 s]
[INFO] JIRA High Availability Control Plugin (Parent) ..... SUCCESS [  1.783 s]
[INFO] JIRA High Availability Control Plugin .............. SUCCESS [ 10.119 s]
[INFO] JIRA High Availability Test API .................... SUCCESS [  1.537 s]
[INFO] HA Container API ................................... SUCCESS [  8.778 s]
[INFO] JIRA High Availability Tests ....................... SUCCESS [  7.423 s]
[INFO] HA Container Tests ................................. FAILURE [ 14.617 s]
[INFO] Atlassian JIRA - Testing - Legacy Func Tests ....... SKIPPED
[INFO] Atlassian JIRA - Testing - Embedded Crowd Func Tests SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 23:06 min
[INFO] Finished at: 2017-11-22T13:44:12-08:00
[INFO] Final Memory: 423M/954M
[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack (copy-jira-tomcat-libs) on project ha-container-tests: Unable to find artifact. Could not find artifact com.atlassian.jira:jira-jars-tomcat-di
stribution:zip:tomcat-8x:7.3.5 in atlassian-proxy (https://m2proxy.atlassian.com/repository/public)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,233 views 14 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot