bazel-contrib / bazel-contrib/rules_jvm
Can't clone it in our windows kokoro jobs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 54
- Forks
- 98
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 7
Description
all in the title, this
https://github.com/bazel-contrib/rules_jvm/blob/main/java/test/com/github/bazel_contrib/contrib_rules_jvm/javaparser/generators/workspace/com/gazelle/java/javaparser/generators/AnnotationFromJavaStandardLibrary.java is waaaaaaay too long on windows...
error in kokoro (using our bazel based build of google/or-tools for windows):
WORKSPACE:
git_repository(
name = "contrib_rules_jvm",
tag = "v0.9.0",
#tag = "v0.19.0", # didn't work with junit5
remote = "https://github.com/bazel-contrib/rules_jvm.git",
)
And the kokoro (fusion2 trace)
C:\tmpfs\src>choco install bazel -y -i
....
C:\tmpfs\src>bazel version
Build label: 6.3.2
...
C:\tmpfs\src\git\or-tools>bazel build -c opt -s //ortools/...
...
Error in fail: error running 'git reset --hard tags/v0.9.0' while working with @contrib_rules_jvm:
error: unable to create file java/test/com/github/bazel_contrib/contrib_rules_jvm/javaparser/generators/workspace/com/gazelle/java/javaparser/generators/AnnotationFromJavaStandardLibrary.java: Filename too long
fatal: Could not reset index file to revision 'tags/v0.9.0'.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced AnnotationFromJavaStandardLibrary.java path and the WORKSPACE git_repository declaration, then reproduce the Windows failure with bazel build -c opt -s //ortools/... or an equivalent checkout of tag v0.9.0. Done means the rules_jvm dependency can be fetched and reset successfully in the reported Windows Kokoro environment without the filename-too-long error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100