Open saper opened 9 years ago
Thanks for the issue.
The integration tests are configured to download node. This is based on the behavior of https://github.com/srs/gradle-node-plugin. I can (and might) change that requirement since it is causing problems with Gradle 2.4 as well.
I'm not 100% sure how nebula triggers the gradle run for integration tests, but I think it may be causing issues.
This is duplicate of https://github.com/srs/gradle-node-plugin/issues/50.
Ah, yeah it looks like there isn't a FreeBSD build available on the nodejs website.
No, node
is compiled from source via the FreeBSD ports system: (cd /usr/ports/www/node && make install)
OR the binary is downloaded via the pkg
tool: pkg install node
.
http://pkg.FreeBSD.org/FreeBSD:10:amd64/latest/All/node-0.12.3.txz
is a link for the node 0.12.3 FreeBSD package for FreeBSD 10/amd64. To extract the binary itself, just decompress and untar the file, the binary will be in bin
.
Running on
FreeBSD 10.1/amd64
andMy currently installed node instance (actually this is io.js 2.0.0) identifies the system as:
Exceptions:
Gradle daemon reports on its logs
It seems like node binaries for Linux are downloaded (this is output from
file(1)
folded for readability)and