Alex Nordlund
Alex Nordlund
If you set `download` to `true` this plugin will download `node` and `npm` using the versions provided in the configuration, if you set it to `false` you need to have...
Is this still an issue? I got a local node install and use both this plugin and the community fork just fine
We re-arranged the conditionals and added a `startsWith('aarch')` in the https://github.com/node-gradle/gradle-node-plugin fork, which should hopefully solve this
I have a proposed solution in a fork. https://github.com/node-gradle/gradle-node-plugin/pull/5 If anyone would like to have a look at it that'd be great! The idea is to add a task that...
That's correct, there's no 32bit version of node v10.15.3, if you want to run it on a 32bit system you'll have to pick an earlier version of node.
@paksv probably because it's a 32bit JVM being used. Can you check what ´os.arch´ is being reported by the JVM used by gradle? We've changed this in the fork to...
To be honest, I think this is Working As Intended. Your JVM is reporting 32-bit and 32-bit node is being requested. If you're on a 64-bit system, why not use...
Does it work when you run Gradle from the command-line with a 64-bit JVM? If that doesn't work, check what `os.arch` is being reported and open an issue at the...
Setting `JAVA_HOME` is probably the way to go there, but if `os.arch` returns `amd64` you're supposed to get an x64 distribution of node, that's what's being used to determine which...
Use a 64bit JVM