Incorrect download path for nodejs
See original GitHub issueDo you want to request a feature or report a bug? I believe it is a bug. Please educate me if it is something else.
What is the current behavior? While compiling the Graylog server project (https://github.com/Graylog2/graylog2-server) that uses this plugin, it failed with:
Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.8.0:install-node-and-yarn (install node and yarn) on project graylog2-server: Could not download Node.js: Got error code 404 from the server. -> [Help 1]
and the reason is that it tries to download https://nodejs.org/dist/v12.13.1/node-v12.13.1-linux-x86.tar.gz
and I’m afraid it doesn’t exist.
If the current behavior is a bug, please provide the steps to reproduce.
git clone https://github.com/Graylog2/graylog2-server.git
cd graylog2-server/
mvn clean install
What is the expected behavior? Successfully download the dependency and install it.
Please mention your frontend-maven-plugin and operating system version. In the parent pom:
<!-- Nodejs dependencies -->
<nodejs.version>v12.13.1</nodejs.version>
<yarn.version>v1.19.2</yarn.version>
...
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<version>1.8.0</version>
</plugin>
In the child pom
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<executions>
<execution>
<id>install node and yarn</id>
<goals>
<goal>install-node-and-yarn</goal>
</goals>
<configuration>
<nodeVersion>${nodejs.version}</nodeVersion>
<yarnVersion>${yarn.version}</yarnVersion>
</configuration>
</execution>
<execution>
<id>yarn install</id>
<goals>
<goal>yarn</goal>
</goals>
<!-- Optional configuration which provides for running any npm command -->
<configuration>
<arguments>install</arguments>
</configuration>
</execution>
<execution>
<id>yarn run build</id>
<goals>
<goal>yarn</goal>
</goals>
<configuration>
<arguments>run build</arguments>
</configuration>
</execution>
</executions>
</plugin>
It is a box on AWS running Ubuntu.
ubuntu@ip-10-0-8-52:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
ubuntu@ip-10-0-8-52:~$
Thanks!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:14 (4 by maintainers)
Top Results From Across the Web
change node.js installation directory - Stack Overflow
I downloaded the windows msi of node.js v5.6.0 64bit. When I execute it, it popped up a warning "Invalid E: drive" and shut...
Read more >How to resolve 'node' is not recognized as an internal or ...
Open the Environment Variables option in your Control Panel. · Select the variable named Path. · Restart the command prompt again and now...
Read more >Common errors | npm Docs
You are trying to install on a drive that either has no space, or has no permission to write. Free some disk space...
Read more >Corepack | Node.js v19.2.0 Documentation
Should you experience a problem, run corepack disable to remove the proxies ... Since Corepack usually downloads the package manager releases straight from ......
Read more >Node v12.22.2 (LTS)
More specifically, improper configuration of permissions in the installation directory allows an attacker to perform two different ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just hit the same problem with my M1 on 1.8.0 and after updating to 1.12.0 it works.
The same in Ubuntu 20.20