In order to fix a problem with the symbolic links for node and npm on the Windows platform, Version 1.3.1 of the gradle plugins has been released and the gradle.properties has been updated to reference that version in r58755 in trunk.

Making symbolic links on Windows does not work as well as on non-Windows platforms (requiring some specific permissions to do so and the use of other commands, not supported by Java classes currently), so the change with v1.3.1 is to simply not try to create the links on the Windows platform. For Windows users, I recommend that you remove the .node directory created in <LABKEY_ROOT>. The task that the 1.3 version introduced created that directory with some mysterious system files (node.sys and npm.sys, or something like that) that are nothing like symbolic links and would lead to errors like the following in subsequent builds:

> Task :server:symlinkNode FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':server:symlinkNode'.
> java.nio.file.NotLinkException: The file or directory is not a reparse point.

Removing the <LABKEY_ROOT>/.node directory will make this error go away and the directory should not be created again.

If running npm on the command line, it is still recommended that you put the versions of npm and node that the build is using on your path (That is, you can reference <LABKEY_ROOT>/build/modules/core/.node/node*/bin and <LABKEY_ROOT>/build/modules/core/.node/npm*/bin), but, at the moment, there's little benefit to using symbolic links for that on Windows as the links won't get updated when versions change.