Gunnar Wagenknecht
Gunnar Wagenknecht
I also started to investigate Stardoc for us and quickly ran into this. Currently unable to build because `rules_pkg` also has their `.bzl` files defined with _limited_ visibility.
Is this a matter of enabling the build process to produce the binaries and release them or is the development work necessary to implement missing native support?
As a workaround for now use https://github.com/bazelbuild/rules_java/blob/02df6937cda3f627a47d42391b09b7da0fe3b849/toolchains/default_java_toolchain.bzl#L124 with care
I cloned from this repo 3 days ago. Thus, I think I should have the latest. I did some further investigation, though. It seems that those come from the Drupal...
@jpSimkins Thanks! Didn't know about the hooks. Let me know as soon as there is something to test. I'm happy to run pull requests for testing for you.
Many users probably don't know but the length can be extended. I set mine to 99. Maybe recommend increasing the value and/or just increase it silently?
Well, I wouldn't care if it's silently increased. Frankly, I started to dislike dialogs prompting me for obvious things - especially since I started using OS X. It's probably sufficient...
I wonder if this could be set within the running app from Java? Instance name == workspace name?
Is this a dup of [#8106](https://github.com/bazelbuild/bazel/issues/8106)?
@martindow Any luck experimenting with `--reports-dir` argument for getting a nice report of tests for Jenkins (and other CI systems)?