-
Notifications
You must be signed in to change notification settings - Fork 585
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
FindLocalTools fails to search Paket.exe in Subdirectory #2390
Comments
I'm not sure if this is a bug. Should we really search all directories recursively in the project to find |
@matthid At least there should be an option to set the path to |
@nilshelmig You already can, as almost any API in FAKE there is a |
@matthid |
Now I see, yes we need a fix... |
It is possible to teach If user have {
"version": 1,
"isRoot": true,
"tools": {
"paket": {
"version": "5.223.0",
"commands": [
"paket"
]
},
"fake-cli": {
"version": "5.16.1",
"commands": [
"fake"
]
}
}
} then find it somewhere in Nuget cache, to better call |
Ok thanks for reporting this. I found the root cause, should be fixed in the next release (5.18), sorry for taking a bit longer. I didn't understand the impact initially and overlooked this on 5.17. |
Description
Since Fake 5.16.1 Paket fails to find the local paket tool when it lays in a subdirectory. e.g.
<project>/someFolder/.paket/paket.exe
Repro steps
Use Fake.Dotnet.Paket 5.16.1 and have the .paket folder in a subdirectory. Then run
Paket.restore
Expected behavior
Paket runs and all packages are restored
Actual behavior
Fake fails with following error:
Known workarounds
Change version of Fake.DotNet.Paket in build.fsx.lock to 5.16.0
Related information
The text was updated successfully, but these errors were encountered: