Closed jma7889 closed 4 years ago
Try searching for "4.2.1" in your whole code base, does it appear anywhere?
This not in my whole repository, or two mvn projects it depends. But there are more deeper projects dependency that is not exposed. Is there a way to force install of a specific node version?
the issue is resolved, I don't know why, but some minor changes to the pom.xml is required
here's the working pom
<executions>
<execution>
<!-- optional: you don't really need execution ids, but it looks nice in your build log. -->
<id>install-node-and-npm</id>
<phase>generate-resources</phase>
<goals>
<goal>install-node-and-npm</goal>
</goals>
<!-- optional: default phase is "generate-resources" -->
<configuration>
<nodeVersion>v12.18.3</nodeVersion>
<npmVersion>6.14.4</npmVersion>
</configuration>
</execution>
<execution>
<id>npm-install</id>
<goals>
<goal>npm</goal>
</goals>
<!-- optional: default phase is "generate-resources" -->
<phase>generate-resources</phase>
<configuration>
<!-- optional: The default argument is actually
"install", so unless you need to run some other npm command,
you can remove this whole <configuration> section.
-->
<arguments>install</arguments>
</configuration>
</execution>
</executions>
That's strange, but I'm happy to see that you resolved it!
No matter how do I configure it, it always install node v4.2.1
And result: