| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Note that it is currently only used by the java_proto_library family of rules (if enabled per flag).
RELNOTES: None
PiperOrigin-RevId: 208601730
|
|
|
|
|
| |
RELNOTES: none.
PiperOrigin-RevId: 206035881
|
|
|
|
|
|
|
| |
Java code.
RELNOTES: None
PiperOrigin-RevId: 204471346
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202360925
|
|
|
|
|
|
| |
RELNOTES[INC]: The $(JAVA_TRANSLATIONS) Make variable is not supported anymore.
PiperOrigin-RevId: 201278971
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 199382344
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 198911668
|
|
|
|
|
|
|
|
|
| |
to check the direct dependencies for aar_import targets.
Currently the default value of this flag is not changed. And it will be enabled in a separate cl.
RELNOTES: None
PiperOrigin-RevId: 193959866
|
|
|
|
|
|
| |
Always use the more-qualified class name for clarity at the site of use. There are too many classes named Builder.
PiperOrigin-RevId: 193649193
|
|
|
|
|
|
|
|
|
| |
BuildConfiguration.Fragment#compatibleWithStrategy().
The experiment did not work out.
RELNOTES: None.
PiperOrigin-RevId: 192567832
|
|
|
|
|
|
|
| |
checking for aar_import and java_import targets.
RELNOTES:None.
PiperOrigin-RevId: 188399775
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187936071
|
|
|
|
| |
PiperOrigin-RevId: 187397314
|
|
|
|
|
|
| |
Generalizes @AutoCodec.Constructor to @AutoCodec.Instantiator.
PiperOrigin-RevId: 183702768
|
|
|
|
|
|
|
| |
JavaConfiguration.
RELNOTES: None.
PiperOrigin-RevId: 181593727
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 181579365
|
|
|
|
|
|
| |
handled separately).
PiperOrigin-RevId: 180974083
|
|
|
|
| |
PiperOrigin-RevId: 174818556
|
|
|
|
|
|
|
|
| |
to blaze to allow us to toggle off enforcement of the one version property
while building java tests.
RELNOTES: n/a
PiperOrigin-RevId: 173578269
|
|
|
|
|
|
|
| |
This migration flag only affects Java rules.
RELNOTES: None.
PiperOrigin-RevId: 171026607
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--plugin, though once used for C++, is currently a Java-specific flag.
--plugin_copt is currently a total no-op, and has been for a long time.
Moving these to the Java fragment is a little neater and helps get one
step closer to enforcing LateBoundDefault fragment access.
Additionally, since the "no plugins with duplicate names" restriction
was added to work with plugin_copt, this restriction can be lifted.
It no longer adds any value.
RELNOTES: None.
PiperOrigin-RevId: 169981221
|
|
|
|
|
|
|
| |
J2ObjcAspect ignores them.
RELNOTES: None
PiperOrigin-RevId: 164335492
|
|
|
|
|
|
|
|
|
|
| |
Fixes #3295.
Users requested this [1] and it is useful for example to pass it as a value to java_common.compile#strict_deps.
[1] https://stackoverflow.com/questions/44827704/bazel-can-a-skylark-action-read-a-command-line-flag-strict-java-deps
PiperOrigin-RevId: 160886151
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/4929ad79865f8c13ef3b33c827040f4a037e4afe
And use params files for turbine actions with transitive classpaths
For actions where direct deps cannot be used, turbine spawns should always use
params files. The transitive classpath may exceed the command line length
limit.
PiperOrigin-RevId: 159473987
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks dozens of targets in the nightly with Tool Failure errors
*** Original change description ***
Clean up turbine action creation
Support disabling javac fallback for actions without a direct
classpath, and only use the 'JavacTurbine' mnemonic for spawns
that require javac-turbine due to annotation processing to make
it easier to collect metrics on that.
Finally, remove --java_header_compilation_direct_classpath now
that it has been productionized and enabled by default.
PiperOrigin-RevId: 159260596
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support disabling javac fallback for actions without a direct
classpath, and only use the 'JavacTurbine' mnemonic for spawns
that require javac-turbine due to annotation processing to make
it easier to collect metrics on that.
Finally, remove --java_header_compilation_direct_classpath now
that it has been productionized and enabled by default.
PiperOrigin-RevId: 158359858
|
|
|
|
| |
PiperOrigin-RevId: 155223937
|
|
|
|
|
|
| |
updates --experimental_one_version_enforcement from a boolean flag to a 3-state enum (OFF, WARNING, ERROR).
PiperOrigin-RevId: 154978203
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The experiment did not succeed. It is valid for the fallback to succeed if
the original failure was due to a Strict Java Deps error, so enabling
this feature as it is currently implemented is not possible.
PiperOrigin-RevId: 154948042
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note 1) Explanation of the flags:
--explicit_java_test_deps: This is a flag independent of the others, and forces users to specify the JUnit deps. We should try to make this flag default to true in a future release, irrespective of the work around persistent java tests.
--experimental_testrunner: Bazel-only flag affecting switching from the BazelTestRunner to the ExperimentalTestRunner which will run the tests in a separate classloader. --explicit_java_test_deps is desired for this to ensure once we split the classpaths of the TestRunner and the TestTarget, the TestTarget does not hit a ClassNotFoundException, due to missing JUnit deps.
--test_strategy=experimental_worker: This is the existing flag, which in turn depends on --experimental_testrunner flag, since only the ExperimentalTestRunner is capable to running java tests persistently.
Note 2) There was no clean way to check for the flags defined in JavaOptions within TestActionBuilder (as I was checking the "tag=experimental_testrunner" before), without making TeasActionBuilder's build rules depend on java rules (yikes!). Hence, I created a new method compatibleWithStrategy() within each fragment, so I could check if WorkerTestStrategy could be compatible with the user specified flags. Thanks to Greg for suggesting this approach!
RELNOTES: None
PiperOrigin-RevId: 151729869
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151170448
MOS_MIGRATED_REVID=151170448
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 149789440
MOS_MIGRATED_REVID=149789440
|
|
|
|
|
|
|
|
|
| |
They were only used by a test that can just as well use the tokenized
version of the javacOpts.
--
PiperOrigin-RevId: 149102073
MOS_MIGRATED_REVID=149102073
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
To deprecate that flag, we need to fix #2539 first.
*** Original change description ***
Deprecate the legacy_java_test flag, now that nolegacy_java_test has been the default for quite a while now.
RELNOTES[INC]: legacy_java_test flag will not have any effect now.
--
PiperOrigin-RevId: 148107667
MOS_MIGRATED_REVID=148107667
|
|
|
|
|
|
|
|
|
|
| |
the default for quite a while now.
RELNOTES[INC]: legacy_java_test flag will not have any effect now.
--
PiperOrigin-RevId: 147851661
MOS_MIGRATED_REVID=147851661
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rules: If the collection of jars for a java_binary contain more than one
instance of the same class, one of them will be arbitrarily loaded at runtime.
This is problematic if the instances of the class are not identical, as methods
or fields from one class version might be missing in the other, leading to
runtime failures when methods are missing.
This change adds an experimental flag to enable one version enforcement. The
actual enforcement tool will come later.
--
PiperOrigin-RevId: 147166361
MOS_MIGRATED_REVID=147166361
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146143641
MOS_MIGRATED_REVID=146143641
|
|
|
|
|
|
|
|
|
|
| |
Resolves #2363
RELNOTES: Remove support for --javawarn; use e.g. --javacopt=-Xlint:all instead
--
PiperOrigin-RevId: 144652008
MOS_MIGRATED_REVID=144652008
|
|
|
|
|
|
|
|
| |
to only contain direct dependencies.
--
PiperOrigin-RevId: 143557048
MOS_MIGRATED_REVID=143557048
|
|
|
|
|
|
|
|
| |
--
Change-Id: I9ec3209a69ba5a51943b334f278ba93d67d4f9f4
Reviewed-on: https://cr.bazel.build/8090
PiperOrigin-RevId: 143470915
MOS_MIGRATED_REVID=143470915
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 143434756
MOS_MIGRATED_REVID=143434756
|
|
|
|
|
|
|
| |
--experimental_optimize_header_compilation_annotation_processing
--
MOS_MIGRATED_REVID=137035372
|
|
|
|
|
|
|
| |
Use TARGET_CPU instead; they always have the exact same value.
--
MOS_MIGRATED_REVID=132547819
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
appears in the jdeps file. These are the minimum inputs needed by the
JavaCompileAction to obtain the correct result when classpath order and source
files remain unchanged. Uses existing --java_classpath flag to toggle between
'javabuilder' (current released behavior) and new 'experimental_blaze' (minimum classpath
and Spawn inputs). Handles failure of minimal action by falling back to existing
compilation behavior when needed. The new Spawn does not use a parameter file,
but puts all arguments directly on the command line.
--
MOS_MIGRATED_REVID=131109163
|
|
|
|
|
|
|
|
|
| |
Control strict-deps through a rule-level and a package-level attribute, allowing finer-grained migration in conjunction with a global flag.
RELNOTES: java_proto_library: control strict-deps through a rule-level and a package-level attribute.
--
MOS_MIGRATED_REVID=128542363
|
|
|
|
|
|
|
| |
RELNOTES: New rule, java_proto_library, to generate Java bindings for protocol-buffers.
--
MOS_MIGRATED_REVID=127136894
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126310706
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This attribute marks annotation processors that generate API code.
If a rule uses an API-generating annotation processor, other rules depending on
it can refer to the generated code only if their compilation actions are
scheduled after the generating rule.
In the future, annotation processors will only be considered by header
compilation if they set generates_api=1.
--
MOS_MIGRATED_REVID=126152384
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126081020
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top, and finishes replacing them with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}.
RELNOTES: Replace --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
--
MOS_MIGRATED_REVID=120154954
|