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

Want to keep packages folder in root path or How to used paket.references in Group reference #2025

Closed
aarunraja opened this issue Jul 17, 2018 · 4 comments
Labels

Comments

@aarunraja
Copy link

Description

Want to keep all my dependence (package folder) in root folder only. used paket.references to achieve, but getting FileNotFoundException: Could not find file '..\script\paket.dependencies error.

Repro steps

I have folder structure as specified below.
src
--> script
--> build.fsx
--> fake.cmd
--> paket.references
--> svc
--> packages
--> paket.dependencies

the script folder will have F# Make script. in that i have refer my group packet. the code snap given below
#r "paket: groupref build //"

My paket.references will look like this

// [ FAKE GROUP ] group Build source https://api.nuget.org/v3/index.json nuget Fake.Core.Target

when i try to run my script getting below error
There was a problem while setting up the environment:
-> FileNotFoundException: Could not find file '..\script\paket.dependencies'.

Expected behavior

All my dependence should be in root folder only (package folder). the script should run with all it dependence .

Actual behavior

Getting FileNotFoundException: Could not find file '..\script\paket.dependencies error.

Known workarounds

we can reference the components by Absolute Path.

need a document or reference how i can use Absolute Path.

Sample code available here

@matthid matthid added the bug label Jul 18, 2018
@matthid
Copy link
Member

matthid commented Jul 18, 2018

Yes this scenario should work... PR is welcome but will take a look eventually.

@matthid matthid mentioned this issue Jul 22, 2018
@matthid
Copy link
Member

matthid commented Jul 29, 2018

Ah it took me a while to realize what the actual failure was because it was working on my end:

  1. git clone ...
  2. cd folderStrct
  3. fake run script/build.fsx <- works as expected
  4. cd script
  5. fake run build.fsx <- fails as discussed above

So there is your first workaround: Change your working directory (honestly that is probably what you want anyway)... Investigating further

@matthid
Copy link
Member

matthid commented Jul 29, 2018

(Btw: Your script misses a call to Target.runOrDefault "All" at the end to actually do something)

@matthid
Copy link
Member

matthid commented Jul 29, 2018

Ok this should work properly with the next release. You might need to delete the .fake directory. Thanks for the report.

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

No branches or pull requests

2 participants