aboutsummaryrefslogtreecommitdiffhomepage
path: root/src
Commit message (Collapse)AuthorAge
...
* Deletes unused code: ArtifactIdRegistry, ArtifactSerializer / Deserializer.Gravatar shahan2018-01-15
| | | | PiperOrigin-RevId: 181975994
* Support patches in http_archiveGravatar Klaus Aehlig2018-01-15
| | | | | | | | | | | Support applying a sequence of patches for external repositories imported via http_archive. (Note that we only support the version from @bazel_tools, not the deprecated native rules.) Works towards #3395. Change-Id: I96c746acc04790b051eb686856c04a3ff3c90059 PiperOrigin-RevId: 181975322
* Export the runfiles path of the JVM executable to Skylark.Gravatar lberki2018-01-15
| | | | | RELNOTES: None. PiperOrigin-RevId: 181973847
* Disable test_actions_deleted_after_execution_nobatch_keep_analysisGravatar dslomov2018-01-15
| | | | | RELNOTES: None. PiperOrigin-RevId: 181971087
* Regression test for #3656.Gravatar Dmitry Lomov2018-01-15
| | | | | Change-Id: Id3d6e6da60aca3c02c7cf3e9e727ecbf177dde66 PiperOrigin-RevId: 181971084
* java,runfiles: cut all third-party dependenciesGravatar Laszlo Csomor2018-01-15
| | | | | | | | | | | | | Cut all dependencies of the Java runfiles library, so we can include its sources in @bazel_tools, and any Java project can safely depend on it without worrying about pulling in an incompatible version of Guava for example. See https://github.com/bazelbuild/bazel/issues/4460 Change-Id: I4a9314c56a2c9dc3afdf53669429750d8fb81e3b PiperOrigin-RevId: 181968558
* Mark tests that inherit BuildViewTestCase as smallGravatar ulfjack2018-01-15
| | | | | | | The default is SMALL, and for better or worse, we mark BuildViewTestCase tests as small, and BuildIntegrationTestCase tests as medium. PiperOrigin-RevId: 181966013
* actions,temp: respect TMPDIR envvarGravatar Laszlo Csomor2018-01-15
| | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/4376 Change-Id: Id78bb0930044626304e54f07735db4d4b2c84720 PiperOrigin-RevId: 181959528
* Do not crash if 'bind' and external repo generate the same //external: target.Gravatar Dmitry Lomov2018-01-15
| | | | | | | | | | Work towards #3676. The behavior is still incorrect (we should in fact disallow this), but at least there is no hard crash. Change-Id: I5181dba73ad725d20b2ea82b2f19e86664b9dbff PiperOrigin-RevId: 181954820
* windows,tests: enable some tests on WindowsGravatar Laszlo Csomor2018-01-15
| | | | | | | | | | | | Add ":windows_tests" and ":all_windows_tests" rules to these packages, and include them in the parent packages. Fixes https://github.com/bazelbuild/bazel/issues/4127 See https://github.com/bazelbuild/bazel/issues/4292 Change-Id: I9c454ed21f47feb8e88e1c25b1e4fa216baa38f6 PiperOrigin-RevId: 181951525
* Properly report missing external repositiones during pattern evaluation.Gravatar Dmitry Lomov2018-01-15
| | | | | | | Fixes #3836. Change-Id: Icc9e8e08c4336fc20f46b6b878986b991d62ab18 PiperOrigin-RevId: 181949937
* Remove some unnecessary depsGravatar Ulf Adams2018-01-15
| | | | | | | | | Change-Id: Ib8dd9265b18fa0915f52427567845105fcdfa295 Closes #4447. Change-Id: Ib8dd9265b18fa0915f52427567845105fcdfa295 PiperOrigin-RevId: 181943004
* Clean up after ↵Gravatar cushon2018-01-15
| | | | | | https://github.com/bazelbuild/bazel/commit/3864a45afa368473a4a6a90d69edb48cb67d367a PiperOrigin-RevId: 181940016
* windows,tests: enable some foundation testsGravatar Laszlo Csomor2018-01-15
| | | | | | | | | | | | | | | Split //src/test/j/c/g/d/b/lib:foundations_test into smaller tests, and enable many of them on Windows. Some tests are still tagged as "no_windows", either because they depend on ":unix", or because we need to fix them to pass on Windows. See https://github.com/bazelbuild/bazel/issues/4292 Change-Id: Ibfab568a9e7b939c40f1301c9cfe06e60302755c PiperOrigin-RevId: 181936880
* Add a TODOGravatar cushon2018-01-14
| | | | PiperOrigin-RevId: 181908311
* Introduce the blaze cquery command as the new ui for configurable query.Gravatar juliexxia2018-01-12
| | | | | | | | | | | | | | | | | | before: blaze build --nobuild //foo --experimental_post_build_query="deps(//foo)" after: blaze cquery "deps(//foo)" pros of ui change: - more concise - assumes query expression targets == targets to be built (but allows for flexibility through --top_level_targets flag) - separate from build command - cquery command recognizes query options, build options, and its own unique set of options cons of ui change: - adds another command to blaze - recognizes options that don't actually work yet -> requires more option validation RELNOTES: None PiperOrigin-RevId: 181816980
* Encapsulate SkylarkInfo layouts in a classGravatar brandjon2018-01-12
| | | | | | | | | This avoids invalid layouts (non-sequential map values), and provides better separation between a layout's representation as a map and its view as a list. Also removed a factory method that's unnecessary, now that the plan is not to closely tie SkylarkInfo to SkylarkProvider. RELNOTES: None PiperOrigin-RevId: 181807071
* PiperOrigin-RevId: 181797878Gravatar Googler2018-01-12
|
* Adds FileSystem check to Path.CODEC.serialize.Gravatar shahan2018-01-12
| | | | PiperOrigin-RevId: 181797078
* Avoid mixing -source and --releaseGravatar cushon2018-01-12
| | | | | | | | 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
* Honor repository when checking for conflictsGravatar Klaus Aehlig2018-01-12
| | | | | | | | | | When checking for conflicts between an input and an output file of a rule, honor the repository the label belongs to. It is a perfectly valid use case to create one file from an equally named (including path) in a different repository. Change-Id: I3aaa99eaa0c473ec31c5cc77beacf657c41ef56d PiperOrigin-RevId: 181761940
* Change packaging rules to operate on strings instead of path fragments.Gravatar tomlu2018-01-12
| | | | | | | | | | | | The upcoming path refactor will normalize all path fragments upon creation. That is fine 99% of the time, but sometimes we want to disallow non-normalized paths on rule attributes. Even this isn't usually a problem since we can validate the string prior to putting it in a path fragment. However, in the case of the packaging rule we do not know the rules of validation until the packaging rule is *consumed* by some other rule. Therefore, retain input as a string on these rules all the way through. We don't really do a lot of path fragmenty stuff with these strings. The main drawback is losing a bit of type safety / readability. SKIP_KOKORO PiperOrigin-RevId: 181760613
* Remove isMainRepo from Root.Gravatar tomlu2018-01-12
| | | | | | This is no longer used. PiperOrigin-RevId: 181754475
* Clean up Windows config_settingsGravatar Yun Peng2018-01-12
| | | | | | | | | | | | | | 1.Deleted config_setting for --cpu=x64_windows_msys, because we don't build Bazel with MSYS gcc anymore. 2.Deleted config_setting for --cpu=x64_windows_msvc, because it uses exactly the same toolchain as --cpu=x64_windows, it'll be removed in the future. This change reduces the complexity of our BUILD files and make them less confusing. Change-Id: I939831a6861413b0f745fb1be98aacd4fb780e0a PiperOrigin-RevId: 181751853
* RELNOTES: Allow expanding TreeArtifacts for libraries_to_linkGravatar Googler2018-01-12
| | | | PiperOrigin-RevId: 181750466
* C++: Only call link() in cc_binary when linkCompileOutputSeparately is true.Gravatar plf2018-01-12
| | | | | | | | | Also rename setLinkType() to setStaticLinkType() in CcLibraryHelper to make it clear that we are setting the specific linking type for the static library. This is an improved version of https://github.com/bazelbuild/bazel/commit/a705eaa9225ff8a03975c8cb49faa6b2899e398d which was rolled back due to a previous conflicting CL causing problems in the nightly. RELNOTES:none PiperOrigin-RevId: 181746447
* Always use the JavaIO VFS implementation in the remote worker.Gravatar John Millikin2018-01-12
| | | | | | | | | | | | The JNI implementation doesn't work from a deployable jar. Fixes https://github.com/bazelbuild/bazel/issues/3249 cc @ulfjack Closes #4438. PiperOrigin-RevId: 181746081
* windows: fix --symlink_prefix=/ throwing exceptionGravatar laszlocsomor2018-01-12
| | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/4421 RELNOTES: none PiperOrigin-RevId: 181742216
* java,runfiles: add Java library to handle runfilesGravatar Laszlo Csomor2018-01-12
| | | | | | | | | | | | | | This is a prerequisite to port all tests to run on Windows. It is also part of the effort to provide platform-independent, language-specific runfiles-handling libraries. See: - https://github.com/bazelbuild/bazel/issues/4292 - https://github.com/bazelbuild/bazel/issues/3839 Change-Id: Ic64aadcf3f97885de3151da9f921d6351687dce9 PiperOrigin-RevId: 181727511
* Make FileSymlinkException and InconsistentFSException IOExceptionsGravatar ulfjack2018-01-12
| | | | | | | Most places handle them the same way as IOException, which seems like a safe default. The places that do care can still throw or catch the more specific type. PiperOrigin-RevId: 181719688
* Simplify root relative path calculation.Gravatar tomlu2018-01-12
| | | | | | This is a first-class artifact concept. No need to go the long way to get this path. PiperOrigin-RevId: 181717016
* Fix breakage caused by unknown commitGravatar cushon2018-01-12
| | | | PiperOrigin-RevId: 181703395
* Require --javacopts to be terminated with --Gravatar cushon2018-01-11
| | | | PiperOrigin-RevId: 181687846
* Remove trivial instances of FileSystem#getRootDirectory from testing code.Gravatar tomlu2018-01-11
| | | | PiperOrigin-RevId: 181686136
* Factor out InMemoryFileSystem's use of root directory.Gravatar tomlu2018-01-11
| | | | | | When there is no root directory this minimises the size of the change required to keep InMemoryFileSystem working. PiperOrigin-RevId: 181685159
* Add support for native header outputs to {java,android}_libraryGravatar cushon2018-01-11
| | | | PiperOrigin-RevId: 181684446
* Stop including BuildConfiguration inside ConfiguredTargetKey: it's too ↵Gravatar janakr2018-01-11
| | | | | | heavyweight. For now, put a BuildConfigurationValue.Key in there. In the future, we may want to put some kind of "delta" key in. PiperOrigin-RevId: 181673805
* Plumb exec root through to all spawn runners.Gravatar tomlu2018-01-11
| | | | | | They need this to parse input manifests. Previously we would grab the exec root from the Root, but wish to unsupport this. PiperOrigin-RevId: 181669143
* Propagate depsObjcProvider from loadable_bundle apple_binary targetsGravatar cparsons2018-01-11
| | | | | | | This fixes a regression introduced by some prior refactoring work. RELNOTES: None. PiperOrigin-RevId: 181665047
* Simplify SkylarkRuleContext#getBuildFileRelativePath.Gravatar tomlu2018-01-11
| | | | | | We don't need to construct roots to relativize a path. PiperOrigin-RevId: 181661592
* Convert ActionLookupKey implementations to directly implement SkyKey, ↵Gravatar janakr2018-01-11
| | | | | | removing the layer of indirection of getting SkyKey out of ActionLookupKey, which uses more memory for no reason. PiperOrigin-RevId: 181658615
* Remove unused code from AndroidIdeInfoProvider.Gravatar tomlu2018-01-11
| | | | PiperOrigin-RevId: 181657963
* Move custom err msg functionality from Info to SkylarkInfoGravatar brandjon2018-01-11
| | | | | | | Info objects no longer store a string pointer for their error message format, which is almost always the same as the one specified by their provider type. Only map-based SkylarkInfo used this (for fancy built-in structs like ctx.attr), so the field is pushed down to there. RELNOTES: None PiperOrigin-RevId: 181654641
* Final cleanup of android_resourcesGravatar Googler2018-01-11
| | | | | RELNOTES: none PiperOrigin-RevId: 181653922
* Remove BuildConfigurationValue#Key#enableActions field. Saves 8 bytes of ↵Gravatar janakr2018-01-11
| | | | | | memory and some work: BuildOptions#equals and #hashCode already take that value into account, so pulling it out does nothing but slow us down during Key construction. PiperOrigin-RevId: 181645301
* Remove some trivally unneeded usages of FileSystem#getRootDirectory.Gravatar tomlu2018-01-11
| | | | | | Windows doesn't have a root directory, so this abstraction doesn't make sense and should be removed. PiperOrigin-RevId: 181638749
* Use Path#createDirectoryAndParents in SkylarkRepositoryContext.Gravatar tomlu2018-01-11
| | | | PiperOrigin-RevId: 181638689
* Remove use of Path#isRootDirectory from BlazeDirectories.Gravatar tomlu2018-01-11
| | | | | | It was put there to support "/" as the workspace. Checking for a null parent will do the same thing. PiperOrigin-RevId: 181638375
* Adds a CODECs for Package and PackageValue.Gravatar shahan2018-01-11
| | | | PiperOrigin-RevId: 181624201
* Concatenate reference config files in singlejarGravatar Tony Liang2018-01-11
| | | | | | | | | | | 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
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-02 01:16:08 +0000