You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Vikas Kumar (Jira)" <ji...@apache.org> on 2022/09/13 10:05:00 UTC
[jira] [Created] (RANGER-3908) Ranger "Security Admin Web Application" module build is failing on Apple M1 Chip machine
Vikas Kumar created RANGER-3908:
-----------------------------------
Summary: Ranger "Security Admin Web Application" module build is failing on Apple M1 Chip machine
Key: RANGER-3908
URL: https://issues.apache.org/jira/browse/RANGER-3908
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 2.3.0
Environment: Apple M1 (Chip) Pro MacOS
Reporter: Vikas Kumar
While building latest ({*}master{*} branch) Ranger, I started getting following build error :
Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:install-node-and-npm *(install node and npm)* on project security-admin-web: *Could not download Node.js: Got error code 404 from the server.*
Module Failed: *Security Admin Web Application*
Command executed: mvn -DskipTests=true clean compile package install assembly:assembly
*Self Analysis:* Further I found security-admin module was trying to download node plugin that actually doesn't exists.
Following is the trace from build log.
*INFO*] *---* frontend-maven-plugin:1.6:install-node-and-npm *(install node and npm)* @ security-admin-web *---*
[*INFO*] Installing node version v8.12.0
[*INFO*] Downloading *https://nodejs.org/dist/v8.12.0/node-v8.12.0-darwin-arm64.tar.gz* to /Users/vikaskr/.m2/repository/com/github/eirslett/node/8.12.0/node-8.12.0-darwin-arm64.tar.gz
[*INFO*] No proxies configured
[*INFO*] No proxy was configured, downloading directly
*Possible RCA:* It could be due to my machine configuration which is *"Apple M1 (Chip) Pro".* Maven is trying to download the ARM64 based artifact but NodeJS v16.0.0 onwards has such artifacts ([https://nodejs.org/dist/v16.0.0/)]
After updating the version in pom.xml, it worked.
<nodeVersion>v16.9.1</nodeVersion>. // existing version is v8.12.0
<npmVersion>7.24.2</npmVersion>. // existing version is 6.4.1
Either nodeJS and npm versions should be updated or it should be made configurable to pass the version through mvn command line.
Please suggest if any work around (or such configurations ) already exists.
h1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)