-
Notifications
You must be signed in to change notification settings - Fork 163
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
improve starlark-in-java installation documentation #24
Comments
Java implementation is not easy to reuse due to dependencies on Bazel. As part of the cleanup, the interface might change. Once we have a clear separation, we'll provide documentation for it. |
Instructions if you want to experiment with it:
Edit. updated the last commands (thanks to Josh) |
**Related issues:** - add -c flag [#35](bazelbuild/starlark#35) - improve starlark-in-java installation documentation [#24](bazelbuild/starlark#24) **Examples:** $ bazel run :Starlark -- -c "print(1)" 1 $ bazel run :Starlark -- -c "print(1)" arg3 USAGE: Starlark [-c "\<cmdLineProgram\>" | \<fileName\>] Closes #7683. PiperOrigin-RevId: 239028987
The Java implementation now has no dependencies on Bazel proper, and now uses the
|
**Related issues:** - add -c flag [#35](bazelbuild/starlark#35) - improve starlark-in-java installation documentation [#24](bazelbuild/starlark#24) **Examples:** $ bazel run :Starlark -- -c "print(1)" 1 $ bazel run :Starlark -- -c "print(1)" arg3 USAGE: Starlark [-c "\<cmdLineProgram\>" | \<fileName\>] Closes #7683. PiperOrigin-RevId: 239028987
Any update, in 2023, on this issue ? |
Both the Go and the Rust implementation of starlark have installation instructions. The Java implementation does not. It'd be nice to fill out the Java installation docs. It's not obvious to me where those docs belong (here? in a readme in https://github.com/bazelbuild/bazel/tree/master/src/main/java/com/google/devtools/skylark? in a separate/new repo just for java starlark?), but it'd be nice to have them somewhere.
The text was updated successfully, but these errors were encountered: