Apache Zeppelin 0.8.0构建失败求助及版本发布时间咨询

Release Date for Zeppelin 0.8.0 #

First off, Apache Zeppelin 0.8.0 was officially released on January 31, 2018 — that lines up with the timestamp in your npm log (March 2018) being shortly after the release, which makes sense for early adopters hitting setup kinks.

Fixing npm Errors During Maven Build #

I see you've already tried switching Node.js and npm versions, but still hit errors when running mvn clean package -DskipTests. Let's break down actionable steps to diagnose and fix this:

1. Stick to the Officially Recommended Node/NPM Versions #

Zeppelin 0.8.0 has strict frontend environment requirements — it’s tested and supported with Node.js 6.x (e.g., 6.14.4) and npm 3.x. Newer versions (like Node 8+ or npm 4+) often introduce compatibility issues with the old dependency tree used in this release.

• Use a version manager like nvm to switch to Node 6.x:

  nvm install 6.14.4
  nvm use 6.14.4
  

• Clear npm’s cache to avoid stale packages:

  npm cache clean --force
  

2. Dig Into the npm Debug Log #

The log at /root/.npm/_logs/2018-03-22T10_38_10_265Z-debug.log holds the key to the exact issue. Open it up and look for common red flags:

• Failed package downloads: If you see errors about missing packages or timeout issues, switch to a more stable npm registry:

  npm config set registry https://registry.npmmirror.com/
  

  Then delete the node_modules folder and package-lock.json (if present) in the zeppelin-web module, and re-run npm install.
• Dependency conflicts: Look for lines mentioning "version mismatch" or "unmet peer dependency". You can resolve this by adding a resolutions field to zeppelin-web/package.json to force a compatible version, e.g.:

  "resolutions": {
    "some-conflicting-package": "1.2.3"
  }
  

• Permission issues: Running as root can trigger npm’s security restrictions. Try adding the --unsafe-perm flag when installing dependencies:

  npm install --unsafe-perm
  

3. Build the Web Module Separately First #

Instead of running the full Maven build right away, isolate the frontend build to narrow down problems:

1. Navigate to the web module directory:

   cd zeppelin-web
   

2. Clean up previous build artifacts:

   rm -rf node_modules target
   

3. Install dependencies and build manually:

   npm install
   npm run build
   

If this fails, you’ll get a clearer error message directly from npm, rather than filtered through Maven. Once this succeeds, go back to the root directory and re-run your Maven command.

4. Force Maven to Use Your Local Node/NPM #

Sometimes Maven tries to use its own bundled Node.js version instead of your local one. Explicitly specify the paths to your Node and npm executables in the Maven command:

mvn clean package -DskipTests -Dnode.executable=$(which node) -Dnpm.executable=$(which npm)

内容的提问来源于stack exchange，提问作者Madiha Khalid