experimental_java_library_export_do_not_use -- new interface planned?

[Kathrin Paschen]

Hi,

I've been looking at an idea that might require me to write a custom java_library rule. In order to make this easy for myself, I would like to be able to call bazel_java_library_rule, which is not currently exported by default.

I came across the flag experimental_java_library_export, which makes the experimental_java_library_export_do_not_use module available, through which I can use bazel_java_library_rule.

Of course, I would rather not rely on a module whose name includes "do_not_use".

The comment over the export statement says "In the future, Build API team will provide an interface that is conceptually similar to this one and stable", which sounds promising.

Is there a plan for that interface yet? 

Thanks,

Kathrin