Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with new Gulp file #171

Open
Sally-Xu opened this issue Aug 9, 2015 · 12 comments
Open

Issues with new Gulp file #171

Sally-Xu opened this issue Aug 9, 2015 · 12 comments

Comments

@Sally-Xu
Copy link
Contributor

Sally-Xu commented Aug 9, 2015

Just updated the latest Fayde project, Looks like you switched from Grunt to Gulp now. Somehow running Gulp reset or symlink only creates empty lib structure under the testsite, test and stress, but no files under those folders.

Looks like Gulp symlink has a problem, here is the error message:

cmd.exe /c gulp -b "D:\Project\FaydeProject\Fayde" --color --gulpfile "D:\Project\FaydeProject\Fayde\Gulpfile.js" symlink-testsite
[11:58:54] Using gulpfile D:\Project\FaydeProject\Fayde\Gulpfile.js
[11:58:54] Starting 'symlink-testsite'...
[11:58:54] gulp-symlink:D:\Project\FaydeProject\Fayde\lib\minerva symlinked to testsite\lib\minerva
[11:58:54] 'symlink-testsite' errored after 44 ms
[11:58:54] Error in plugin 'gulp-symlink'
Message:
EEXIST, symlink 'D:\Project\lib\minerva'
Details:
errno: 47
code: EEXIST
path: D:\Project\lib\minerva
[11:58:54] gulp-symlink:D:\Project\FaydeProject\Fayde\lib\nullstone symlinked to testsite\lib\nullstone
[11:58:54] gulp-symlink:D:\Project\FaydeProject\Fayde\lib\perfex symlinked to testsite\lib\perfex
[11:58:54] gulp-symlink:D:\Project\FaydeProject\Fayde\lib\requirejs symlinked to testsite\lib\requirejs
[11:58:54] gulp-symlink:D:\Project\FaydeProject\Fayde\lib\requirejs-text symlinked to testsite\lib\requirejs-text
[11:58:54] gulp-symlink:D:\Project\FaydeProject\Fayde\dist symlinked to testsite\lib\fayde\dist

Looks like it is not looking for the correct lib path.

@BSick7
Copy link
Member

BSick7 commented Aug 9, 2015

Are you using visual studio to run?

Try running gulp reset from the command line. Of that works, then we can narrow in on the problem.

@Sally-Xu
Copy link
Contributor Author

Sally-Xu commented Aug 9, 2015

yes, I'm using visual studio's task runner.

@Sally-Xu
Copy link
Contributor Author

Sally-Xu commented Aug 9, 2015

Tried to run gulp reset from command line, still not working. I can see testsite/lib/minerva folder, but when I cd to this folder, then run "dir" command, I got this:

dir : Could not find a part of the path 'D:\Project\FaydeProject\Fayde\testsite\lib\minerva'.
At line:1 char:1

  • dir
  • - CategoryInfo          : ReadError: (D:\Project\Fayd...ite\lib\minerva:String) [Get-ChildI
      Exception
    - FullyQualifiedErrorId : DirIOError,Microsoft.PowerShell.Commands.GetChildItemCommand
    
    

When I run "Dir" under testsite/lib folder, I can see lib/fayde is a directory. but other folders are created as "Junction", they are pointing to D:\Project\lib\XXX which doesn't exist. They should be pointing to the lib folder under the Fayde project which is "D:\Project\FaydeProject\Fayde\lib\XXX" in my case.

screenshot

@BSick7
Copy link
Member

BSick7 commented Aug 10, 2015

Please try with latest.

@Sally-Xu
Copy link
Contributor Author

Still not working. Still pointing to D:\Project\lib\XXX.

@BSick7
Copy link
Member

BSick7 commented Aug 11, 2015

Can you run node -v and npm -v?

@Sally-Xu
Copy link
Contributor Author

node -v : v0.10.28
npm -v: 1.4.9

@Sally-Xu
Copy link
Contributor Author

Just updated node to v0.12.7 and npm to v.2.11.3.

still not working.

@BSick7
Copy link
Member

BSick7 commented Aug 11, 2015

I was able to reproduce it. Are you using win10?

@BSick7
Copy link
Member

BSick7 commented Aug 11, 2015

Found the issue to this. gulp-symlink uses symlinks as a first attempt. It falls back to using junctions which do not support relative symlinks. Since Fayde is using relative symlinks, it's intepreting the link incorrectly.

I will work on converting symlinks to absolute to resolve this later.

@BSick7
Copy link
Member

BSick7 commented Aug 11, 2015

As a workaround, run this with admin privileges. The symlink attempt is failing due to a permissions issue.

@Sally-Xu
Copy link
Contributor Author

yup, that worked. I usually always set to open visual studio as admin. I just forgot to do that after installing vs 2015.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants