| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 206085005
|
|
|
|
| |
PiperOrigin-RevId: 206025645
|
|
|
|
|
|
| |
non-generated source are generated.
PiperOrigin-RevId: 205756917
|
|
|
|
|
|
|
|
|
|
|
| |
now that the bootstrap build uses the VanillaJavaBuilder it is compatible
with the host JDK's javac, and avoiding -Xbootclasspath/p makes the
bootstrap build more compatible with JDK 9.
See #5521
RELNOTES: N/A
PiperOrigin-RevId: 205605294
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Follow-up to commit 09d20311d982606093ed881d779bb05a5ee70ed3.
Use try-with-resources to ensure Writer objects
are closed eagerly.
Eagerly closing Writers avoids hanging on to
file handles until the garbage collector finalizes
the object, meaning Bazel on Windows (and
other processes) can delete or mutate these files.
Hopefully this avoids intermittent file deletion
errors that sometimes occur on Windows.
See https://github.com/bazelbuild/bazel/issues/5512
RELNOTES: none
PiperOrigin-RevId: 203934471
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Follow-up to commit 59f17d6e0550bf63a0b6ef182e2d63474e058ede.
Use try-with-resources to ensure Reader objects
are closed eagerly.
Eagerly closing Readers avoids hanging on to
file handles until the garbage collector finalizes
the object, meaning Bazel on Windows (and
other processes) can delete or mutate these files.
Hopefully this avoids intermittent file deletion
errors that sometimes occur on Windows.
See https://github.com/bazelbuild/bazel/issues/5512
RELNOTES: none
PiperOrigin-RevId: 203771262
|
|
|
|
| |
PiperOrigin-RevId: 202577988
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 202404085
|
|
|
|
| |
PiperOrigin-RevId: 202162534
|
|
|
|
|
|
|
| |
As //tools/defaults will be deprecated soon. All usages of //tools/defaults:jdk and //tools/defaults:java_toolchain should be replaced by corresponding targets in //tools/jdk/BUILD package
RELNOTES:none
PiperOrigin-RevId: 202114489
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Bazel client on Windows is now 50% faster to
check the embedded tools than it was before.
Results:
- Linux: 20 ms -> 6 ms
- Windows: 294 ms -> 133 ms
Measurements were done with n=10 runs and a hot
server, using blaze::GetMillisecondsMonotonic().
Previously the client performed the same tasks
multiple times while trying to determine if a path
was a good extracted binary. (E.g. converted the
path to Windows format multiple times, checked if
it was a directory twice, opened the path twice.)
Now the client performes these tasks only once,
e.g. it converts path once and stats only once.
See https://github.com/bazelbuild/bazel/issues/5444
Closes #5445.
PiperOrigin-RevId: 201913758
|
|
|
|
|
|
|
| |
Fixes #5418
RELNOTES: N/A
PiperOrigin-RevId: 200934846
|
|
|
|
| |
PiperOrigin-RevId: 200760220
|
|
|
|
|
|
| |
add_dep uses this information for j_p_l rules.
PiperOrigin-RevId: 200721230
|
|
|
|
|
|
|
|
|
|
|
| |
for each test instead of the same directory for all the tests. The previous implementation was using one directory for instrumenting the classes of a jar. For each each jar the metadata directory was deleted if it already existed. This is problematic for local execution when multiple tests are run in parallel because some threads will try to delete the directory and some will try to perform read/write operations on it.
This is an important fix for Bazel coverage users.
Fixes #4398.
RELNOTES: Java coverage works now with multiple jobs.
PiperOrigin-RevId: 199764483
|
|
|
|
|
|
|
| |
the dependency problems.
RELNOTES: None.
PiperOrigin-RevId: 199170334
|
|
|
|
|
|
| |
This CL aslo enables a presubmit check for correct formatting of all bzl files in //third_party/bazel.
PiperOrigin-RevId: 198857055
|
|
|
|
|
|
|
|
|
| |
necessary. If we stop resolving the super classes, then the checker will
complain that some methods are missign. In fact, these methods exist, but their
class is not resolved due to the existing early-break strategy.
RELNOTES: none
PiperOrigin-RevId: 198594008
|
|
|
|
|
|
| |
Fixes #5260
PiperOrigin-RevId: 198110476
|
|
|
|
|
| |
RELNOTES:none.
PiperOrigin-RevId: 197923013
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 196272337
|
|
|
|
| |
PiperOrigin-RevId: 196266567
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/5157
If a user's default system locale is not `en`, `en_US` or `en_UK`, there may be a chance that `String#toUpperCase` will result in a string that does not exist in the Enum declaration. This is the case in #5157.
To fix this, it's either
1) setting the Locale in the individual `toUpperCase` calls or
2) set Locale to English by default from `Bazel.java`.
I chose the first because it seemed less intrusive, but I'm open to suggestions.
Closes #5184.
PiperOrigin-RevId: 196261078
|
|
|
|
| |
PiperOrigin-RevId: 195732395
|
|
|
|
| |
PiperOrigin-RevId: 195090893
|
|
|
|
| |
PiperOrigin-RevId: 195040539
|
|
|
|
|
| |
RELNOTES:none.
PiperOrigin-RevId: 194598332
|
|
|
|
|
|
|
| |
jdeps proto without emitting any warning or error.
RELNOTES: none.
PiperOrigin-RevId: 194593178
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/bdb75bba00dbe97e9bb99db04844096f135f59ad
PiperOrigin-RevId: 194559167
|
|
|
|
| |
PiperOrigin-RevId: 194512971
|
|
|
|
| |
PiperOrigin-RevId: 194504697
|
|
|
|
| |
PiperOrigin-RevId: 194503531
|
|
|
|
|
| |
RELNOTES:
PiperOrigin-RevId: 194461881
|
|
|
|
|
|
| |
Always use the more-qualified class name for clarity at the site of use. There are too many classes named Builder.
PiperOrigin-RevId: 193579440
|
|
|
|
|
|
|
| |
This code was failing to reset the SJD plugin before falling back, which
caused a reference to a JimFS Path in the original filesystem to leak.
PiperOrigin-RevId: 193421565
|
|
|
|
|
|
|
|
| |
2. Remove incorrect assertion in AnnotationVisitor.visit(String, Object), and
delegate the checking for arrays to visitArray(String).
RELNOTES: n/a.
PiperOrigin-RevId: 193256108
|
|
|
|
| |
PiperOrigin-RevId: 193052121
|
|
|
|
|
|
|
|
|
| |
previously --release always took precedence.
if/when Bazel defaults to using e.g. --release 9, legacy -source and -target
javacopts should be respected.
PiperOrigin-RevId: 192844963
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 192844304
|
|
|
|
| |
PiperOrigin-RevId: 192837552
|
|
|
|
|
| |
RELNOTES: n/a.
PiperOrigin-RevId: 192836316
|
|
|
|
|
|
|
|
|
| |
together) into two separate classpaths. This is the preparation cl. In the
following cls, I will graduately make the dependency issues clear, i.e., wether
it is a problem in the bootclasspath or the regular classpath.
RELNOTES: n/a.
PiperOrigin-RevId: 192828237
|
|
|
|
| |
PiperOrigin-RevId: 192802011
|
|
|
|
| |
PiperOrigin-RevId: 192539741
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 192452316
|
|
|
|
| |
PiperOrigin-RevId: 191970818
|
|
|
|
| |
PiperOrigin-RevId: 191961686
|
|
|
|
| |
PiperOrigin-RevId: 191948995
|
|
|
|
| |
PiperOrigin-RevId: 191809494
|
| |
|