-
Notifications
You must be signed in to change notification settings - Fork 275
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
Possible confusion in the docs //scala:scala.bzl vs @io_bazel_rules_scala//scala:scala.bzl #60
Comments
you can see this error btw in my getting started scala repo (https://github.com/ittaiz/bazel-scala-getting-started) |
Hi, definitely explaining correct use is in scope for the repo, but I'm a little unclear what your question is.
If it is the latter, I 100% support adding "getting started" section to the README.md. If it is the former, I'm not sure what the style is. Is referring to targets with the full name allowed? I have never tried. For clarity, it might be good to use the full name, if that indeed works (I was somehow initially under the impression that names were only for remote repos, but it does seem like it should work if you were designing the feature). PRs on both issues are warmly welcomed! :) |
Excellent. My initial idea was to have a separate "test application" which might sit
|
Tried using the full name and didn't work |
There is bind, which allows you to basically make a solid link but that Maybe you can ask on the bazel list. I guess you cannot refer to the On Monday, May 23, 2016, Ittai Zeidman notifications@github.com wrote:
P. Oscar Boykin, Ph.D. | http://twitter.com/posco | http://pobox.com/~boykin |
I'll ask and update here
|
fixes #60 by clarifying the getting started path
Do you want me to keep investigating the full name?
|
First of all thanks a lot for all your hard work, it's really appreciated!
I'm not sure this is in the scope of this repo but the fact of the matter is that I went along the readme and since it mentions the
load
with respect toprelude_bazel
I wasn't sure if there isn't a different syntax for that use-case.I went to the tests since they are the executable specification and failed since they use the absolute(?) path
//scala:scala.bzl
This is an on-boarding issue since if I was familiar with Bazel syntax well enough I wouldn't have made that mistake but I think we want to make on-boarding easier.
2 options I had in mind:
The added value of add support for src jars #2 is that it serves as a bit of a test application since it has to use the syntax like "regular" users.
I'd be happy to contribute both options but didn't want to barge in with a PR before we discuss it.
The text was updated successfully, but these errors were encountered: