You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I explicitly specify a target on the command line which is also a dependency of another target I specify on the command line, it should only run that target once.
Instead it seems it runs a target once per target on the command line
In light of the post about co-maintainers ... if I find some time to work on this (it's admittedly a pretty small issue and doesn't really get in my way 😉) I'll see if I can put up a PR for it 🙂
Since clean obviously removes all build, test and pack output, I end up without any build, or pack output if I run the targets in wrong order.
For example if I do mage build pack test I end up with only the test results left. If I want a fast run, so also build is only done once I need to run mage test pack and not calling the build target (directly) at all. And in this case my test result files get lost.
I mean, yes we can workaround it. And since go compiles fast it's not even so bad to run the build twice. But hey, targets and resolving the dependencies between them is kind of a core feature of make file like systems.
So if somebody has a hint for me how to fix this, I may give it a try.
If I explicitly specify a target on the command line which is also a dependency of another target I specify on the command line, it should only run that target once.
Instead it seems it runs a target once per target on the command line
Example
magefile.go
:Invocation:
mage a b
Expected:
Actual:
More fun:
I'd expect this to be equivalent to just running
mage a b
, which should be functionally equivalent to runningmage b
The text was updated successfully, but these errors were encountered: