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
Ever since commit dec2e39, *every* **make**(1) target would result in
running `nuget restore`, e.g.:
$ make run-tests TESTS=bin/TestDebug/Java.Interop.Tools.JavaSource-Tests.dll
nuget restore
...
The `nuget restore` was both time consuming and irrelevant, and meant
that `make` targets which *should* have been fast -- like `make all`,
which shouldn't do anything after the initial `make prepare all`,
would instead take multiple seconds to complete.
Why was `nuget restore` always being invoked?
$ make -d -n run-tests
...
Must remake target `packages/NUnit.3.11.0/NUnit.3.11.0.nupkg'.
nuget restore
What happened is that commit dec2e39 changed various projects to be
Short-Form SDK projects, which in turn alters the `packages` directory
structure: instead of e.g.
packages/NUnit.3.11.0/NUnit.3.11.0.nupkg
the file is instead:
packages/nunit/3.11.0/nunit.3.11.0.nupkg
Note case and directory structure change, which in turn meant that the
rule dependencies were *never* satisfied (unless you happened to have
a `packages` directory from a pre-dec2e390 build…).
We *could* fix up the `$(PACKAGES)` and `$(NUNIT_CONSOLE)` variables
to use the new paths, but they're not actually *used* for anything
anymore, so just remove them.
0 commit comments