-
Notifications
You must be signed in to change notification settings - Fork 586
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
--single-target is not working #594
Comments
do you have mini repro? |
test.cmd@echo off ".\tools\NuGet\NuGet.exe" "install" "FAKE" "-OutputDirectory" ".\bin\tools" "-ExcludeVersion" "-Prerelease" SET TARGET="Build" IF NOT [%1]==[](set TARGET="%1") ".\bin\tools\FAKE\tools\Fake.exe" "test.fsx" "target=%TARGET%" -st applicationName=MyApp PAUSE test.fsx#I @"./bin/tools/FAKE/tools/" open Fake let applicationName = getBuildParamOrDefault "applicationName" "" Target "Clean" (fun _ -> trace "Clean...") Target "Build" (fun _ -> Target "RestorePackages" (fun _ -> Target "CreateNuGet" (fun _ -> // Dependencies // start build |
Works for me in version 3.27.5 with both |
I can confirm the problem. Normally |
I confirm the problem too. Easily reproducable by calling e.g. |
also hitting this issue whenever I specify a parameter it ignores -st, is there a workaround? |
--single-target works great for me
|
@cdroulers Am I doing something wrong?
the build.cmd file is like this:
|
No idea. I use fake.exe and --single-target and it works. But with -st, it
|
Can you hive us working sample? -----Original Message----- No idea. I use fake.exe and --single-target and it works. But with -st, it
— |
I think this will work for you if you change the command line to use the "modern" options. Your current usage is a mix of the two. This should work.
There are some docs here too. |
Print a warning when fail to parse command line args with Argu. We still fall back to try and run with the pre-2.1.8 argument style. Extracted exception formatting from the traceException function, so it could be used when tracing an exception as a warning. This should help avoid confusion, as witnessed in fsprojects#1072 and fsprojects#594.
Print a warning when fail to parse command line args with Argu. We still fall back to try and run with the pre-2.1.8 argument style. Extracted exception formatting from the traceException function, so it could be used when tracing an exception as a warning. This should help avoid confusion, as witnessed in fsprojects#1072 and fsprojects#594.
Print a warning when fail to parse command line args with Argu. We still fall back to try and run with the pre-2.1.8 argument style. Extracted exception formatting from the traceException function, so it could be used when tracing an exception as a warning. This should help avoid confusion, as witnessed in fsprojects#1072 and fsprojects#594.
Print a warning when fail to parse command line args with Argu. We still fall back to try and run with the pre-2.1.8 argument style. Extracted exception formatting from the traceException function, so it could be used when tracing an exception as a warning. This should help avoid confusion, as witnessed in fsprojects#1072 and fsprojects#594.
@mynkow can we close this issue? |
It seems #1301 will finally solve this 😄 |
I've just tested this. It is working now. Thank you. |
That escalated quickly 😃 |
It always execute the dependencies. I have tried all possible combinations.
The text was updated successfully, but these errors were encountered: