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
There are several reason that seems to prevent me to use this module within another module (not the root module).
1.If this dep is instantiated in more than one module, the repository named "doxygen" will be created twice, resulting in a name conflict:
doxygen_repository(
Error in repository_rule: A repo named doxygen is already generated by this module extension at /home/me/.cache/bazel/_bazel_me/a3aa740f2f5594e9ea9a176330f7930a/external/rules_doxygen+/extensions.bzl:268:27
If I try to instanciate it only in a non-root module, it will complain that the repository @doxygen is not visible from @@//.
(17:58:17) ERROR: no such package '@@[unknown repo 'doxygen' requested from @@]//': The repository '@@[unknown repo 'doxygen' requested from @@]' could not be resolved: No repository visible as '@doxygen' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
Tested with bazel 8.0.0
The text was updated successfully, but these errors were encountered:
Thanks for the report.
First of all, I would suggest adding dev_dependency = True whenever you import rules_doxygen, unless some of the exposed targets need it. This should immediately solve your issue.
If that is not possible, I am introducing a new repository tag that will allow you to give different names to the @doxygen repository, to ensure no conflicts arise. See #17 for more details and let me know if this works for you.
There are several reason that seems to prevent me to use this module within another module (not the root module).
1.If this dep is instantiated in more than one module, the repository named "doxygen" will be created twice, resulting in a name conflict:
Tested with bazel 8.0.0
The text was updated successfully, but these errors were encountered: