-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Transitive dependencies of nuget packages don't contribute to build #413
Comments
The repo appears to be private. You can override this by using |
We also have the |
I made the repo public - apologies. I am using the transitive/strict dependency checking for Java and C++, and it's very useful there, so I'd rather not disable it for C# (but it does fix the build problem here). It is a viable workaround for now though that is unblocking me. For 3rdparty dependencies to be useful, groups should indeed have |
Hi,
I'm running into a problem with using the
xunit
package from nuget with the paket/bazel integration.The xunit package is itself empty, as far as I'm aware, and transitively depends on
xunit.core
, which in turn depends onxunit.extensibility.core
which has the actual DLL which dotnet needs to compile against.I have setup a simple project at https://github.com/criemen/rules-dotnet-repro, which compiles with
dotnet build
, but fails to compile withbazelisk build //:Program
, as bazel can't find theXunit
namespace.Looking into
Program.dll-0.params
, this seems to be the case as the transitive dependencyxunit.extensibility.core
doesn't contribute its DLL to the build invocation.Adding
@paket.main//xunit.extensibility.core
to the deps of the project fixes the build, as expected.As this is an implementation detail of the
xunit
package, as user I don't want to think about that and specify that dependency by hand.The text was updated successfully, but these errors were encountered: