-
Notifications
You must be signed in to change notification settings - Fork 15
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
Broken path / reference to proto files when used as a Bazel dependency #114
Comments
In hope, that it will help debugging, I'll add some more infos I found. So, most probably the
Which produces the following output when running the js-dossier build directly :
And the following output when running as a dependency :
I'm definitely not a Bazel, Skylark, etc. expert. Just a humble user. But as a layman this doesn't look good. |
I get the same behavior if by experiment I change my genrule definition :
console out :
|
Maybe I'm getting closer to the solution, maybe not, but I'll leave this link here, in case it'd be helpful : https://stackoverflow.com/questions/55796252/how-to-write-bazel-rules-that-work-with-external-repositories |
Now I give up for a while. It seems like these could be related :
I'll attempt to fall back to using an old version of js-dossier on your repo, that was published as a jar, and revisit this problem later. I would love to fix it myself, but I just couldn't. Spent a few days on it with no result (but at least I learned a lot about the internals of Bazel, and its surroundings). |
Issue Summary
Hi!
I tried to integrate js-dossier as a dependency to generate some nice docs for the project.
The plan which by my opinion should work is to load the dependencies of js-dossier; load it as an
http_archive
, and use//src/java/com/github/jsdossier:dossier
as a genrule tool.I've been tinkering with a fork in my workspace so far, to expose
//src/java/com/github/jsdossier:dossier
as public, and to make js-dossier's dependencies easily loadable using a customdossier_repositories()
call (parameterized, as it seems to be a best practice by observation).Issue Details
Steps to reproduce
@my_local_dependency_reference//src/java/com/github/jsdossier:dossier
as agenrule
toolMy debug purpose genrule definition
I know this genrule as it is wouldn't generate the docs, but I fail to even refer to the dossier jar, as it break while it loads.
Assumed main / root error message
../adam_rocska_jsdossier/src/proto/dossier.proto: No such file or directory
Output Log
The text was updated successfully, but these errors were encountered: