| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
The values (if present) are written into the manifest with this format:
Target-Label: <label>
Injecting-Rule-Kind: <kind>
In the future, JavaBuilder will make sure of this instead of command line arguments to find owners for jars for its add_dep commands.
PiperOrigin-RevId: 185557317
|
|
|
|
|
|
| |
Fixes #4614
PiperOrigin-RevId: 185474153
|
|
|
|
|
|
|
|
| |
2) Also print the dependency issues to stderr.
3) Add golden tests to test the above two.
RELNOTES:n/a.
PiperOrigin-RevId: 185423338
|
|
|
|
| |
PiperOrigin-RevId: 185419668
|
|
|
|
|
| |
Change-Id: I1fa7867ffb08af95c1eef5ae3e32cff34292328b
PiperOrigin-RevId: 185189976
|
|
|
|
|
| |
RELNOTES:none.
PiperOrigin-RevId: 185075745
|
|
|
|
| |
PiperOrigin-RevId: 185003013
|
|
|
|
|
|
|
| |
series. The following CLs will integrate this into bazel.
RELNOTES:n/a.
PiperOrigin-RevId: 184706507
|
|
|
|
| |
PiperOrigin-RevId: 184370036
|
|
|
|
|
|
|
|
| |
To avoid hiding compiler.warn.sun.proprietary warnings when running with -Werror.
Fixes bazelbuild/bazel#4564
PiperOrigin-RevId: 184367653
|
|
|
|
|
|
| |
instead of directJarsToTargets/indirectJarsToTargets.
PiperOrigin-RevId: 183780563
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of passing:
--direct_dependency jar1 jarowner1 aspect1
--indirect_dependency jar2 jarowner2 aspect2
--classpath jar1 jar2
we pass
--dependencies jar1 jarowner1;aspect1 jar2 jarowner2:aspect2
--direct_dependencies jar1
This formats doesn't need to inspect each item in the incoming nested set, and thus doesn't need CustomMultiArgv.
This change needs to be rolled out in phases, so this CL changes JavaBuilder and Turbine to accept either format.
RELNOTES: None
PiperOrigin-RevId: 183155036
|
|
|
|
|
|
| |
Bazel bootstrap.
PiperOrigin-RevId: 183065122
|
|
|
|
|
|
| |
Fixes bazelbuild/bazel#4483
PiperOrigin-RevId: 182847474
|
|
|
|
| |
PiperOrigin-RevId: 182461095
|
|
|
|
| |
PiperOrigin-RevId: 182130131
|
|
|
|
|
|
|
|
| |
javac does not allow both -source and --release to be set, which makes it
difficult to migrate to --release when javacopts are combined from
multiple sources.
PiperOrigin-RevId: 182113897
|
|
|
|
| |
PiperOrigin-RevId: 181908311
|
|
|
|
|
|
|
|
| |
javac doesn't allow both to be set, so when defaulting to target
Java 8 use --release if the javacopts already include a
--release flag.
PiperOrigin-RevId: 181777670
|
|
|
|
| |
PiperOrigin-RevId: 181703395
|
|
|
|
| |
PiperOrigin-RevId: 181687846
|
|
|
|
|
|
|
|
|
|
|
| |
Merge reference.conf files in single jar since [akka will break](https://doc.akka.io/docs/akka/current/general/configuration.html#when-using-jarjar-onejar-assembly-or-any-jar-bundler) if reference.conf files are overwritten.
The feature is added to both java and cpp implementations of singlejar to concatenate reference.conf files to keep behaviors consistent. For the cpp implementation, using `OutputJar.ExtraCombiner` in singlejar_main.cc feels less intrusive than adding a new `Concatenator` in the output_jar code.
Bazel-dev discussion on the issue is [here](https://groups.google.com/forum/#!topic/bazel-dev/C30dwAPL708).
Closes #4413.
PiperOrigin-RevId: 181622277
|
|
|
|
| |
PiperOrigin-RevId: 181180652
|
|
|
|
|
|
| |
javax.annotation.processing.Generated
PiperOrigin-RevId: 181012373
|
|
|
|
|
|
|
| |
instead of emitting them one file at a time. This provides users
with a single add_dep command instead of one-per-file.
PiperOrigin-RevId: 180979982
|
|
|
|
|
|
|
|
| |
Add a --native_header_output flag which, if set, causes JavaBuilder to set
the equivalent of `javac -h`, and then collect all generated headers and
write them to a jar archive at the given path.
PiperOrigin-RevId: 180954084
|
|
|
|
| |
PiperOrigin-RevId: 179841278
|
|
|
|
|
|
|
| |
rt.jar etc. no longer exist, retrieve the default bootclasspath contents
using a Java program instead.
PiperOrigin-RevId: 179747945
|
|
|
|
|
|
|
|
|
|
|
| |
JDK 9 adds javac flags that start with `--`, so we can't assume that `--` flags
belong to JavaBuilder. Instead, we will use `--` by itself as a delimiter to parse
e.g. `--javacopts --release 8 -- sources Hello.java`.
This change just adds support for dropping a trailing `--` after parsing javacopts.
We can't rely on the delimiter until after the next Blaze release.
PiperOrigin-RevId: 179589863
|
|
|
|
|
|
| |
and replace the only use with java_common.default_javac_opts.
PiperOrigin-RevId: 179571481
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 178448614
|
|
|
|
| |
PiperOrigin-RevId: 178176824
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/0b2352de3101e87647d083f6089246079dda0f75
PiperOrigin-RevId: 177415788
|
|
|
|
|
|
| |
See bazelbuild/bazel#4165.
PiperOrigin-RevId: 177254510
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/0b2352de3101e87647d083f6089246079dda0f75
PiperOrigin-RevId: 177234776
|
|
|
|
| |
PiperOrigin-RevId: 177138150
|
|
|
|
|
|
| |
Blaze now passes class paths as individual arguments, instead of a pre-joined.
PiperOrigin-RevId: 177112933
|
|
|
|
|
|
| |
This avoids bazelbuild/bazel#4108.
PiperOrigin-RevId: 177096864
|
|
|
|
|
|
|
|
|
|
|
| |
to rules that use the $(JAVA) or the $(JAVABASE) Make variable.
This is necessary because a future Blaze version will require this for rules that use said Make variables. This incompatible change can be tested today by adding the --noexperimental_enable_jvm_configuration_make_variables command line option to Blaze.
This change is part of a large-scale change ([]
RELNOTES: None.
PiperOrigin-RevId: 176834987
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use try-with-resources to close all streams.
I hope this will fix the spurious file deletion
failures on Windows, where the persistent
JavaBuilder worker cannot delete outputs from
previous builds because, supposedly, they are
still open, because a stale object that's ready
to be GC'd hasn't yet been actually GC'd.
Change-Id: Ia57b8bd0ba1b6ee0691d34467c92e86e35d4d71d
PiperOrigin-RevId: 175941520
|
|
|
|
| |
PiperOrigin-RevId: 175709097
|
|
|
|
| |
PiperOrigin-RevId: 174354036
|
|
|
|
|
|
|
|
|
| |
This happens when a sh_test has a dependency on a java_binary, so
JACOCO_METADATA_JAR is not set and coverage should not be run on the
java_binary.
RELNOTES: None.
PiperOrigin-RevId: 172881410
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 172545302
|
|
|
|
| |
PiperOrigin-RevId: 172365313
|
|
|
|
| |
PiperOrigin-RevId: 171245323
|
|
|
|
| |
PiperOrigin-RevId: 171209823
|
|
|
|
| |
PiperOrigin-RevId: 170960535
|
|
|
|
| |
PiperOrigin-RevId: 170752570
|
|
|
|
|
|
|
|
|
| |
as it was not part of a valid junit xml schema.
To cherry-pick for #3286.
RELNOTES: None.
PiperOrigin-RevId: 170022796
|