Skip to content

aspect based proto rules #548

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

Closed
johnynek opened this issue Jun 28, 2018 · 5 comments
Closed

aspect based proto rules #548

johnynek opened this issue Jun 28, 2018 · 5 comments

Comments

@johnynek
Copy link
Contributor

similar to #524 do the same for proto rules to fix the same issues.

@ittaiz
Copy link
Contributor

ittaiz commented Jun 30, 2018

What problems exactly? Because proto doesn't use the extra_information it just uses the transitive proto sources from the proto provider

@johnynek
Copy link
Contributor Author

johnynek commented Jul 9, 2018

I think that currently the proto rules rebuild the transitive closure of all protos on each invocation.

That is not what you want. It means unless you make sure you have no overlaps (your proto_library forms a tree, not a DAG), you will duplicate class files in the jars across targets.

@johnynek
Copy link
Contributor Author

johnynek commented Jul 9, 2018

actually, it does not look like it has that bug, but you do need to manually build the graph correctly.

The aspect approach automatically generates a 1 for 1 proto_library to action DAG.

@simuons
Copy link
Collaborator

simuons commented Oct 23, 2020

@ittaiz I think this issue can be closed

@ittaiz ittaiz closed this as completed Oct 23, 2020
@ittaiz
Copy link
Contributor

ittaiz commented Oct 23, 2020

Thanks!

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

No branches or pull requests

3 participants