Fabian Meumertzheim

Could you elaborate on what you would want to use the reproducers for? With the new JUnit plugin and a "standalone jar" version of Jazzer, we are trying to get...

@aiuto The notes for the current release do not have this stanza in the release notes. I would go as far as saying that a repo that is as fundamental...

> How big of an issue this is in practice? One advantage that I see with the Github-generated archives is that their provenance is pretty much clear, as long as...

In my opinion, this feature would be a layering violation: Toolchains should be reusable across projects and should thus not encode assumptions about the source file path layout of a...

We could build arbitrary logic into rules_cc to handle WORKSPACE repos, so yes, we could cover this. Maybe @meteorcloudy also has some more insights into this interaction of C++ feature...

@meteorcloudy That sounds tricky indeed. But since features are essentially a C++/Objc-only mechanism, we could just have the relevant rules read the result of the module extension and add the...

Could you check whether this is fixed by https://github.com/bazelbuild/bazel-gazelle/pull/1604?

> Let me phrase it differently. How do i check if it fixed it? You have to update the `http_archive` you use to bring in `bazel_gazelle` to point to a...

This archive would require a `strip_prefix` to be usable, so I suspect that there is an earlier definition of this repo in your WORKSPACE file that takes precedence or that...

Relevant slack thread: https://bazelbuild.slack.com/archives/C014RARENH0/p1704836682274409?thread_ts=1700623974.089569&cid=C014RARENH0