Skip to content
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

scala_proto should require JavaInfo provider and not specific rules #650

Merged
merged 2 commits into from
Dec 12, 2018

Conversation

ittaiz
Copy link
Member

@ittaiz ittaiz commented Dec 11, 2018

subj.
drive-by: removed old conditional.
@laurentlb @dslomov I really wanted to use ProtoSourcesProvider and not "proto" like the docs say but as far as I can see ProtoSourcesProvider isn't defined as a symbol. Also see bazelbuild/bazel#3701 and bazelbuild/bazel#3527
Can anyone help us move to the correct pattern?

@ittaiz
Copy link
Member Author

ittaiz commented Dec 11, 2018

by the way, my motivation came from the need to depend on scala_import and so that is the test I added. I decided to implement the generic best practice solution of providers since allow_rules is specific and deprecated. https://docs.bazel.build/versions/master/skylark/lib/attr.html

@ittaiz ittaiz mentioned this pull request Dec 11, 2018
@ittaiz
Copy link
Member Author

ittaiz commented Dec 12, 2018

@johnynek any thoughts? I'd like to merge this since this is blocking us

@johnynek
Copy link
Member

Thanks @ittaiz

@ittaiz ittaiz merged commit 5130b97 into master Dec 12, 2018
@ittaiz ittaiz deleted the scala_proto_providers branch December 12, 2018 07:45
@ittaiz
Copy link
Member Author

ittaiz commented Dec 12, 2018

Thank you!
@laurentlb @dslomov if we can still get your help we'd appreciate it since we'd like to avoid the usage of the legacy providers

@laurentlb
Copy link
Contributor

@c-parsons
@lberki

@lberki
Copy link
Contributor

lberki commented Dec 13, 2018

@iirina

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants