-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Don't link plugin dependencies to products #6695
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
@swift-ci please smoke test |
Seems like the tests are passing, so maybe this was really just a mistake. |
Locally confirmed fixes #6673 (which I initially mis-diagnosed) |
2024a70
to
27c9f48
Compare
@swift-ci please smoke test |
@swift-ci please smoke test windows |
I'd like to add some test coverage for this and we probably also want this fix in 5.9. I am not 100% sure how plugins ever worked with these issues in place 😬 |
27c9f48
to
c5c6777
Compare
I do wonder whether we need to put this fix behind the 5.9 tools-version? At least in theory, it seems like the bug could be load bearing if dependencies ended up being unexpressed because of this. By definition, any package that currently ships couldn't have suffered major consequences from this bug, otherwise it would have been possible to ship said package. |
@swift-ci please smoke test |
Hm, this is legitimate, but I wonder why this issue didn't show up locally? |
@swift-ci please smoke test |
@swift-ci please smoke test windows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small suggestion to improve code readability
This fixes two issues with plugins and their dependencies: - we were traversing plugin products and including their targets as part of any product - since we are including plugin targets as dependencies as well, we could traverse plugin targets in a similarly incorrect way
2d793cd
to
96b7594
Compare
@swift-ci please smoke test |
@swift-ci please smoke test windows |
Windows build failed with
Seems like this isn't entirely a fluke... |
@swift-ci please smoke test windows |
This fixes two issues with plugins and their dependencies:
- we were traversing plugin products and including their targets as part of any product
- since we are including plugin targets as dependencies as well, we could traverse plugin targets in a similarly incorrect way