aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google
Commit message (Collapse)AuthorAge
* Mandatory cfg parameter for labels if executable=1 is providedGravatar Vladimir Moskva2017-01-13
| | | | | | | | RELNOTES[INC]: All executable labels must also have a cfg parameter specified. -- PiperOrigin-RevId: 144332992 MOS_MIGRATED_REVID=144332992
* Refactor NestedSetBuilderGravatar Jon Brandvein2017-01-13
| | | | | | | | Add Order#isCompatible, clean javadoc. Also fix broken @Deprecated-based canary for detecting accidental flattening. -- PiperOrigin-RevId: 144331341 MOS_MIGRATED_REVID=144331341
* AppleCrosstoolTransition turns off any fission modes.Gravatar Cal Peyser2017-01-12
| | | | | | -- PiperOrigin-RevId: 144325333 MOS_MIGRATED_REVID=144325333
* Reduce number of C++ modules explicitly specified on the command line.Gravatar Googler2017-01-12
| | | | | | -- PiperOrigin-RevId: 144323833 MOS_MIGRATED_REVID=144323833
* Rollback of commit 7fc35ae6890f4130b4d99a6c5007dcee91c5a8cc.Gravatar Marcel Hlopko2017-01-12
| | | | | | | | | | | | | | | | *** Reason for rollback *** Breaks //src/test/java/com/google/devtools/build/lib:bazel-rules-tests http://ci.bazel.io/view/Dashboard/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/lastCompletedBuild/console *** Original change description *** aar_import provides JavaCompilationArgsProvider for DexArchiveAspect. -- PiperOrigin-RevId: 144316524 MOS_MIGRATED_REVID=144316524
* Windows, JNI: arg for argv0 in nativeCreateProcessGravatar Laszlo Csomor2017-01-12
| | | | | | | | | | | | | | | | | | | Add a separate argument to nativeCreateProcess for argv[0] specifically, and another for the rest of the args. In a subsequent change I'll add code to compute the 8dot3 style short name of the argv[0] so we can use longer paths for executables in CreateProcessA than we normally could. This is the same approach as used in commit 44ecf9a0c7c25496a43f59f1c8f20df9527e12cb See https://github.com/bazelbuild/bazel/issues/2107 See https://github.com/bazelbuild/bazel/issues/2181 -- PiperOrigin-RevId: 144311562 MOS_MIGRATED_REVID=144311562
* Add a java_{library,binary}.resource_jars attribute that allows one to ↵Gravatar Lukacs Berki2017-01-12
| | | | | | | | specify jar files containing Java resources. -- PiperOrigin-RevId: 144299119 MOS_MIGRATED_REVID=144299119
* Gives 3 levels of sandbox error message under different flags.Gravatar Yue Gan2017-01-12
| | | | | | | | | | | | | | | | | 1. no flag: only the direct reason is given (command execution termination status), and also the instruction to use "--verbose_failures" 2. flag "--verbose_failures": gives failed execution command and the instruction to use "--sandbox_debug --strategy" 3. flag "--verbose_failures --sandbox_debug": gives failed execution command, debugging message from sandboxing, and the instruction to use "--strategy" Also removes "cd <sandbox_path>" in given failed command, since debugging is only necessary with flag "--verbose_failures --sandbox_debug" and the path is already given in sandboxing debugging message. Addresses #2174. Fixes bazel_sandboxing_test.sh and bazel_test_test.sh for the new error message. Fixes timeout. -- PiperOrigin-RevId: 144285435 MOS_MIGRATED_REVID=144285435
* Make android_sdk_repository create one android_sdk per api level in the SDK.Gravatar Adam Michael2017-01-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | api_level is no longer required. It now sets the default android_sdk that is used if the --android_sdk flag is not passed. If it is not set, the highest api_level will be used as the default. The new behavior is demonstrated by the following example: $ ls $ANDROID_HOME/platforms android-21 android-22 android-23 $ cat WORKSPACE android_sdk_repository( name = "foo", ) $ bazel build //java/my/app # uses api level 23 $ bazel build --android_sdk=@foo//:sdk-22 //java/my/app # uses api level 22 $ cat > WORKSPACE <<EOF android_sdk_repository( name = "foo", api_level = 21, ) EOF $ bazel build //java/my/app # uses api level 21 $ bazel build --android_sdk=@foo//:sdk-23 //java/my/app # uses api level 23 See https://github.com/bazelbuild/bazel/issues/2284 for the master plan for android_sdk_repository. RELNOTES: android_sdk_repository no longer requires api_level. If one is not specified, the highest android platform installed will be used. Furthermore, android_sdk's are created for all android platforms installed and can be specified with the --android_sdk flag. -- PiperOrigin-RevId: 144258881 MOS_MIGRATED_REVID=144258881
* aar_import provides JavaCompilationArgsProvider for DexArchiveAspect.Gravatar Adam Michael2017-01-12
| | | | | | -- PiperOrigin-RevId: 144258810 MOS_MIGRATED_REVID=144258810
* Allows a rule class to specify a configuration transtion that will apply to allGravatar Cal Peyser2017-01-12
| | | | | | | | | | incoming edges if dynamic configurations are turned on. This CL does not cover top-level nodes. -- PiperOrigin-RevId: 144258789 MOS_MIGRATED_REVID=144258789
* Consolidate host javabase input lookupGravatar Liam Miller-Cushon2017-01-12
| | | | | | -- PiperOrigin-RevId: 144257691 MOS_MIGRATED_REVID=144257691
* Windows: remove test-specific JNI loaderGravatar Laszlo Csomor2017-01-12
| | | | | | | | | | WindowsJniLoader.loadJniForTesting is just a special case of what WindowsJniLoader.loadJni already does, so we can just use the latter. -- PiperOrigin-RevId: 144224388 MOS_MIGRATED_REVID=144224388
* Deprecate the flags --experimental_skip_unused_modules andGravatar Googler2017-01-12
| | | | | | | | | | --experimental_prune_more_modules. Both flags have proven to be stable for a few weeks. Instead provide a (probably permanent) option to disable modules pruning completely. -- PiperOrigin-RevId: 144215146 MOS_MIGRATED_REVID=144215146
* Add SwiftConfigurationGravatar Dmitry Shevchenko2017-01-12
| | | | | | | | * This new configuration allows for passthrough of Swift-specific options into Skylark for further consumption by swift_library. It also keeps things nicely isolated until we get a way to create configurations in Skylark directly. -- PiperOrigin-RevId: 144210267 MOS_MIGRATED_REVID=144210267
* Rollback of commit 1da8ac3a8bb0780251976e0dbcfebd3a7ba6a066.Gravatar Pedro Liberal Fernandez2017-01-12
| | | | | | -- PiperOrigin-RevId: 144207746 MOS_MIGRATED_REVID=144207746
* Description redacted.Gravatar Googler2017-01-12
| | | | | | -- PiperOrigin-RevId: 144207428 MOS_MIGRATED_REVID=144207428
* Rollback of commit 0d1dc5537903a8c2ad56e66cee129b8f4d4e2592.Gravatar Pedro Liberal Fernandez2017-01-11
| | | | | | -- PiperOrigin-RevId: 144194956 MOS_MIGRATED_REVID=144194956
* Fix bug in --experimental_link_dynamic_binaries_separately.Gravatar Googler2017-01-11
| | | | | | | | | | | | | | | If linkstatic was explicitly set to 0 for a non-test target, we didn't set CcLibraryHelper to create CcLinkOutputs, but would still try to link those in instead of the compile output. Instead, pull out a variable that puts this logic into a single spot. Also rename the flag to --experimental_link_compile_output_separately, which IMO makes slightly more sense. Not too important as I don't think we should keep this flag long-term anyway. -- PiperOrigin-RevId: 144194903 MOS_MIGRATED_REVID=144194903
* Eliminate the $jacoco_runtime implicit attribute and link in the Jacoco ↵Gravatar Lukacs Berki2017-01-11
| | | | | | | | | | agent through the $jacocorunner dependency. They are either both linked in or neither of them is, so there isn't much point in separating them. -- PiperOrigin-RevId: 144191570 MOS_MIGRATED_REVID=144191570
* Add a small helper method to ActionInputHelperGravatar Ulf Adams2017-01-11
| | | | | | | | | | This is part of a series of changes to clean up the test strategies; this specific change is a Google-internal refactoring. I'm planning to also update the external test strategies subsequently. -- PiperOrigin-RevId: 144184752 MOS_MIGRATED_REVID=144184752
* Rollback of commit fa7e34979b1a10794321b1233e8d6f44a62431fa.Gravatar Pedro Liberal Fernandez2017-01-11
| | | | | | -- PiperOrigin-RevId: 144181101 MOS_MIGRATED_REVID=144181101
* Rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.Gravatar Marcel Hlopko2017-01-11
| | | | | | | | | | | | | | | | *** Reason for rollback *** Breaks bazel-docker-tests http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console *** Original change description *** Enable header compilation by default -- PiperOrigin-RevId: 144176396 MOS_MIGRATED_REVID=144176396
* Add a deprecation warning to objc_xcodeprojGravatar Dmitry Shevchenko2017-01-11
| | | | | | -- PiperOrigin-RevId: 144127414 MOS_MIGRATED_REVID=144127414
* Set ios_cpu on child configurations of multi-arch apple rules in all cases.Gravatar Chris Parsons2017-01-10
| | | | | | -- PiperOrigin-RevId: 144108788 MOS_MIGRATED_REVID=144108788
* Remove javac and jar from the Jvm fragmentGravatar Liam Miller-Cushon2017-01-10
| | | | | | -- PiperOrigin-RevId: 144107395 MOS_MIGRATED_REVID=144107395
* Automated [] rollback of commit 56bc3cbf0e87423e815422d1c6e02846af74c0bf.Gravatar Marcel Hlopko2017-01-10
| | | | | | | | | | | | *** Reason for rollback *** Still breaks //src/test/shell/bazel:bazel_test_test http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/lastCompletedBuild/testReport/(root)/(empty)/test_test_timeout/ -- PiperOrigin-RevId: 144107285 MOS_MIGRATED_REVID=144107285
* Rollback of commit 62a6f695f95b8dde15fe9b287a290dc7ac06e173.Gravatar Marcel Hlopko2017-01-10
| | | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Breaks //src/test/shell/bazel:persistent_test_runner_test http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/lastBuild/testReport/junit/(root)/(empty)/test_simple_scenario/ *** Original change description *** Also add the duration as the test process time. Technically, this code is incorrect, because we're calling into spawn strategy, which might do any amount of additional waiting (e.g., to acquire local resources). We should change spawn strategy to return structured information about the subprocess execution, including the wall time, and use that to set the test information. But for now, this seems good enough. Fixes #1748. -- PiperOrigin-RevId: 144096164 MOS_MIGRATED_REVID=144096164
* Skylark repositories: propage value from --action_env to repository_ctx.environ Gravatar Damien Martin-Guillerez2017-01-10
| | | | | | | | | | | | | | | | | | | | | | The environment is now computed with a mixture of the client environment and the values specified by the --action_env flag. If a user want to overwrite its environment for skylark repository, they can do `--action_env FOO=BAR` and the repository will see FOO as having the value BAR, whichever value is set in the client environment. Also propagate it to all repository functions, and deduplicate the way the client environment is passed to repository functions. Design doc: https://bazel.build/designs/2016/10/18/repository-invalidation.html [step 1] RELNOTES[INC]: repository_ctx environment is now affected by --action_env flag (value from the client environment will be replaced by value given on the command line through --action_env). -- Change-Id: I131a9695439aa9949d5001f820e2ae450e41332f Reviewed-on: https://cr.bazel.build/7971 PiperOrigin-RevId: 144091492 MOS_MIGRATED_REVID=144091492
* Finish removing experimental_use_rclass_generator flagGravatar Googler2017-01-10
| | | | | | | | | | | Since it's already a no-op after the latest release this should be harmless... R=ahumesky -- PiperOrigin-RevId: 144088752 MOS_MIGRATED_REVID=144088752
* Refactor StandaloneTestStrategy; tiny step towards test strategy unification.Gravatar Ulf Adams2017-01-10
| | | | | | | | | | Create the test spawn upfront instead of lazily. In the common case, this doesn't cost anything, but the worker test strategy doesn't use the spawn right now. -- PiperOrigin-RevId: 144086321 MOS_MIGRATED_REVID=144086321
* Add new flag to specify if output_licenses attribute should be checked for ↵Gravatar Irina Iancu2017-01-10
| | | | | | | | | | licenses. Also flipped :jvm attribute from HOST to TARGET and set the new flag on it. -- PiperOrigin-RevId: 144084000 MOS_MIGRATED_REVID=144084000
* Also add the duration as the test process time.Gravatar Ulf Adams2017-01-10
| | | | | | | | | | | | | | Technically, this code is incorrect, because we're calling into spawn strategy, which might do any amount of additional waiting (e.g., to acquire local resources). We should change spawn strategy to return structured information about the subprocess execution, including the wall time, and use that to set the test information. But for now, this seems good enough. Fixes #1748. -- PiperOrigin-RevId: 144082073 MOS_MIGRATED_REVID=144082073
* Remove some dead code from StandaloneTestStrategy.Gravatar Ulf Adams2017-01-10
| | | | | | -- PiperOrigin-RevId: 144074221 MOS_MIGRATED_REVID=144074221
* Refactor CcToolchainFeatures.Variables.lookupVariable to produce less garbageGravatar Marcel Hlopko2017-01-10
| | | | | | -- PiperOrigin-RevId: 144072456 MOS_MIGRATED_REVID=144072456
* Expose thinlto_params_file and linker_param_file as build variablesGravatar Marcel Hlopko2017-01-10
| | | | | | | | | This cl exposes param files that were hard-coded before. This enables more precise placement on the link command line. -- PiperOrigin-RevId: 144069927 MOS_MIGRATED_REVID=144069927
* Deprecated and removed HOST_CFG and DATA_CFG global variables.Gravatar Vladimir Moskva2017-01-10
| | | | | | | | RELNOTES[INC]: Deprecated globals HOST_CFG and DATA_CFG are removed. Use strings "host" and "data" instead. -- PiperOrigin-RevId: 144069794 MOS_MIGRATED_REVID=144069794
* Expose methods for the undeclared outputs and annotations directoriesGravatar Ulf Adams2017-01-10
| | | | | | | | | | This is part of a sequence of changes to update the test strategies; most of the actual code changes in this specific change is Google-internal, but I'm planning to update the external test strategies as well. -- PiperOrigin-RevId: 144064802 MOS_MIGRATED_REVID=144064802
* Encapsulate the required provider logic in RequiredProviders class.Gravatar Dmitry Lomov2017-01-10
| | | | | | | | | For now, only for aspects, but eventually expand to Attribute's mandatory providers as well. -- PiperOrigin-RevId: 144063369 MOS_MIGRATED_REVID=144063369
* Gives 3 levels of sandbox error message under different flags.Gravatar Yue Gan2017-01-10
| | | | | | | | | | | | | | | | 1. no flag: only the direct reason is given (command execution termination status), and also the instruction to use "--verbose_failures" 2. flag "--verbose_failures": gives failed execution command and the instruction to use "--sandbox_debug --strategy" 3. flag "--verbose_failures --sandbox_debug": gives failed execution command, debugging message from sandboxing, and the instruction to use "--strategy" Also removes "cd <sandbox_path>" in given failed command, since debugging is only necessary with flag "--verbose_failures --sandbox_debug" and the path is already given in sandboxing debugging message. Addresses #2174. Fixes bazel_sandboxing_test.sh and bazel_test_test.sh for the new error message. -- PiperOrigin-RevId: 144058351 MOS_MIGRATED_REVID=144058351
* Remove the inmemoryfs library from lib:foundationGravatar Ulf Adams2017-01-10
| | | | | | | | No production code should depend on inmemoryfs. -- PiperOrigin-RevId: 144054981 MOS_MIGRATED_REVID=144054981
* Remove the unused class RPCService and its test.Gravatar Lukacs Berki2017-01-10
| | | | | | -- PiperOrigin-RevId: 144054816 MOS_MIGRATED_REVID=144054816
* Description redacted.Gravatar Rumou Duan2017-01-10
| | | | | | -- PiperOrigin-RevId: 144010091 MOS_MIGRATED_REVID=144010091
* Extract a set of advertised providers into a separate class.Gravatar Dmitry Lomov2017-01-10
| | | | | | -- PiperOrigin-RevId: 143991903 MOS_MIGRATED_REVID=143991903
* Expose DEVELOPER_DIR to SkylarkGravatar Dmitry Shevchenko2017-01-10
| | | | | | | | * Also make constants private since they both have getters now. -- PiperOrigin-RevId: 143973536 MOS_MIGRATED_REVID=143973536
* Enable header compilation by defaultGravatar Liam Miller-Cushon2017-01-10
| | | | | | -- PiperOrigin-RevId: 143972504 MOS_MIGRATED_REVID=143972504
* Improve performance and semantics of union of Skylark setsGravatar Jon Brandvein2017-01-10
| | | | | | | | | | | | | | | | | | | | | | == Before this change == Previously, if a and b are sets, then a + b created a new set c whose direct and transitive elements were all those of a, and with b appended as an additional transitive element. If on the other hand b is a list instead of a set, then its contents were appended as additional direct elements of c. In both cases, you can think of c as a copy of a that also knows about b. This copying of a's elements into c can lead to accumulation when you do it repeatedly, e.g. x += y in a loop. Each union can take O(n) time so you get O(n^2) time overall. Nested set union is supposed to be O(1) time per operation and O(n) time overall. It also leads to surprising iteration orders. If you do a + b + c + d (left-associative), where each one is a set, then when you do a post-order traversal you get the elements of b, c, d, and a, in that order. This is because b, c, and d each get appended as transitive children of the copies of a. == After this change == If a and b are sets, then a + b returns a new set c with a and b as its two transitive children. If b is a list, then c has a as its only transitive child and b's elements as its only direct elements. This is straightforward, O(1), and avoids the problem with the confusing order. It is implemented by removing the items/transitiveItems fields and just relying on NestedSetBuilder. RELNOTES[INC]: (Skylark) Set union is now O(1). As a side-effect, the iteration order of sets produced by union has changed. "print(set([1]) + set([2]) + set([3]))" will now give back the order 1, 2, 3 instead of 2, 3, 1. -- PiperOrigin-RevId: 143972165 MOS_MIGRATED_REVID=143972165
* Making it remove @ in module names Gravatar Mike Lewis2017-01-10
| | | | | | | | | | | Fixes #2311 Closes #2312. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2312 PiperOrigin-RevId: 143967880 MOS_MIGRATED_REVID=143967880
* Advertise java Skylark provider from java proto aspects.Gravatar Googler2017-01-10
| | | | | | | | The skylark provider is bound as "proto_java" to avoid collisions with the base, which is called "java". -- PiperOrigin-RevId: 143960605 MOS_MIGRATED_REVID=143960605
* Introduce expand_if_none_available to crosstoolGravatar Marcel Hlopko2017-01-10
| | | | | | | | | | This feature allows us to expand a flag_group when a build variable is not available. This is helpful when migrating crosstools in a backward compatible way (that works with released bazel as well as with bazel at HEAD). -- PiperOrigin-RevId: 143955333 MOS_MIGRATED_REVID=143955333
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-06 11:12:44 +0000