-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Remove aspnet/Scaffolding submodule #7166
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
Conversation
dougbu
commented
Jan 31, 2019
- aspnet/AspNetCore-Internal#1341
- aspnet/AspNetCore-Internal#1341
@natemcmaster I'm seeing the following errors in the CI checks. We previously got versions for these packages from the Scaffolding submodule. I see references to these
|
Separately, has something regressed on the agents we're using? File locking conflict warnings now seem common. |
@dougbu. Yes, remove the lines from artifacts.props. We will treat the scaffolding packages like any other 'external dependency'. You'll need to add variables to build/dependencies.props, such as |
You'll need to remove Scaffolding from these files too: https://github.com/aspnet/AspNetCore/blob/release/2.1/build/submodules.props |
Nevermind |
…uild/submodules.props` and our templates - add versions for these packages in `build/dependencies.props` to enable their inclusion in the package archives
@natemcmaster I see no need for these version variables in |
|
pre-mature ctrl + enter...
No, I think you're right. We can completely remove the variables from 2.2 |
- also Undo `Templating` removal from `build/submodules.props` - this feels wrong but build broke without this line
2f8a293
to
edb10ab
Compare
No longer a WIP and required CI checks have passed. |