| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 206130934
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
extension functions.
PiperOrigin-RevId: 198579700
|
|
|
|
|
|
| |
This is done by adding a --[no]strip_classes flag to ijar.
PiperOrigin-RevId: 191184258
|
|
|
|
|
|
|
| |
This is the convention, and tools that only read manifests may optimize
assuming that the manifest is at the beginning.
PiperOrigin-RevId: 190167351
|
|
|
|
| |
PiperOrigin-RevId: 190010996
|
|
|
|
| |
PiperOrigin-RevId: 185381597
|
|
|
|
| |
PiperOrigin-RevId: 185215813
|
|
|
|
|
|
| |
codec, but whose parent classes have codecs. This is ok because the polymorphic strategy doesn't need an instance of the grandchild class: the parent class is fine, so long as it has a codec.
PiperOrigin-RevId: 185200943
|
|
|
|
| |
Change-Id: Id636879aeab94916fcaed3c067e4077215ebc6df
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a rollforward with fixes.
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: 185159950
|
|
|
|
| |
PiperOrigin-RevId: 185153485
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Cascade rollback to unbreak bazel tests
*** Original change description ***
Update ijar tests to verify time stamp.
***
PiperOrigin-RevId: 185147605
|
|
|
|
| |
PiperOrigin-RevId: 185009133
|
|
|
|
|
|
|
|
|
|
|
| |
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: 185006704
|
|
|
|
|
|
|
|
|
| |
instead of removing them, since builds that use modules need them to be
visible across compilation boundaries. Note that the module-infos don't
contain any implementation that needs to be removed, so ijar just copies
the entire file through.
PiperOrigin-RevId: 184562080
|
|
|
|
|
|
|
|
| |
@damienmg Here are a few more changes. (`third_party` only)
Closes #4164.
PiperOrigin-RevId: 177278511
|
|
|
|
| |
PiperOrigin-RevId: 176987812
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Closes #4052.
Change-Id: I30c4dc047195404a6ff63338ac4a944bb2755a1f
|
|
|
|
| |
PiperOrigin-RevId: 168789962
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is a follow-up to a recent change which allowed LLVM raw profile files
to be directly used with blaze. This change allows zipped LLVM raw profile
files.
This uses //tools/zip:zipper to extract the zipped file contents.
This also adds a new option to //tools/zip:zipper, 'j', to junk directories while
unzipping.
Tested:
blaze test //devtools/blaze/integration:fdo_test
blaze test //third_party/ijar/test:zip_test
RELNOTES[NEW]: Zipped LLVM profiles are now supported.
PiperOrigin-RevId: 158849516
|
|
|
|
|
|
|
| |
This is a prerequisite for the next javac update, and mirrors the
approach used for other javac-based tests in Bazel (e.g.
BazelJavaCompilerTest).
PiperOrigin-RevId: 152779250
|
|
|
|
| |
PiperOrigin-RevId: 151461345
|
|
|
|
|
|
| |
Commit 6d31cb was an internal reorganization of google repository
that should have resulted in no change. Due to a bug in our export
process it deleted several files in third_party.
|
|
|
|
|
| |
PiperOrigin-RevId: 142666783
MOS_MIGRATED_REVID=142666783
|
|
|
|
|
|
|
|
| |
0 is not a valid DOS timestamp, days and months start at 1.
--
PiperOrigin-RevId: 141818782
MOS_MIGRATED_REVID=141818782
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135345337
|
|
|
|
|
|
|
| |
Those tests requires JDK8 features, just ignore them.
--
MOS_MIGRATED_REVID=135264862
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134040102
|
|
|
|
|
|
|
|
|
|
|
| |
Examples for how to use <zip_path>=<file> syntax:
zipper c x.zip a/b/__init__.py= # Add an empty file at a/b/__init__.py
zipper c x.zip a/b/main.py=foo/bar/bin.py # Add file foo/bar/bin.py at a/b/main.py
--
Change-Id: I3c09dfb31d082f3ca8036e87affc8d99f7e75fe0
Reviewed-on: https://bazel-review.googlesource.com/#/c/4243
MOS_MIGRATED_REVID=129325719
|
|
|
|
|
|
|
| |
$TEST_TMPDIR is not deleted automatically and this can result in the accumulation of a bunch of large files on the CI machines of Bazel because this tests writes 2GB files for testing.
--
MOS_MIGRATED_REVID=128037053
|
|
|
|
|
|
|
| |
Another part of rolling forward #1262.
--
MOS_MIGRATED_REVID=125481356
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125160288
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
repositories
One interesting side effect of how this is implemented is that for external
repositories, bin/ and genfiles/ are combined. External repo output is under
bazel-out/local-fastbuild/repo_name for each repo.
Fixes #1262.
RELNOTES[INC]: Previously, an external repository would be symlinked into the
execution root at execroot/local_repo/external/remote_repo. This changes it to
be at execroot/remote_repo. This may break genrules/Skylark actions that
hardcode execution root paths. If this causes breakages for you, ensure that
genrules are using $(location :target) to access files and Skylark rules are
using http://bazel.io/docs/skylark/lib/File.html's path, dirname, etc.
functions.
--
MOS_MIGRATED_REVID=125095799
|
|
|
|
|
|
|
|
|
|
| |
1. Add ability to specify relative output directory through -d option.
2. Add ability to specify a list of archive entries to extract from the zip file.
Fixes #630.
--
MOS_MIGRATED_REVID=122159723
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=121475668
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Bazel's workspace name is now io_bazel. If you are using Bazel's
source as an external repository, then you may want to update the name you're
referring to it as or you'll begin seeing warnings about name mismatches in your
code.
--
MOS_MIGRATED_REVID=120926179
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 790d2f6009d47fe92cf0cd92a1473bbf0141f32e.
*** Reason for rollback ***
Broke non-Bazel projects on ci.bazel.io
Fixes #1168
*** Original change description ***
Move the runfiles for external repositories to under the x.runfiles/ directory
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles....
***
--
MOS_MIGRATED_REVID=120535721
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles.
---
Furthermore, if a Bazel project does not provide a workspace name in the WORKSPACE file, Bazel will now default to using __main__ as the workspace name (instead of "", as previously). The repository's runfiles will appear under x.runfiles/__main__/.
--
MOS_MIGRATED_REVID=120224534
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119581073
|
|
|
|
|
|
|
|
| |
This target include all non tests targets of Bazel to do integration tests of
bootstrapping.
--
MOS_MIGRATED_REVID=115830741
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The JAVAC "Make" variable is the javac packaged with the host JDK, which is not
necessarily the same version used to compile java_library rules.
Users should typically use java_library directly. If a manual javac invocation
is required, BazelJavac uses the same javac version and flags as java_library.
In the rare cases where the host JDK's compiler is actually desired, prefer
`$(JAVABASE)/bin/javac` to `$(JAVAC)` for clarity.
--
MOS_MIGRATED_REVID=113386241
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When creating an archive with //third_party/ijar:zipper, all
files to add should be specified as an argument. When adding a
lot of files, this leads to reaching the maximum size of the
command line.
This change add a @filename argument that permit to specify a
file containing the list of files to zip.
--
Change-Id: I02843588896969ef2d6add26c1c67ff44a27f7de
Reviewed-on: https://bazel-review.googlesource.com/#/c/2695/
MOS_MIGRATED_REVID=112678600
|
|
|
|
|
|
|
|
|
| |
This make those test target compatible with --nolegacy_bazel_java_test.
--
Change-Id: I2316c9aa53327b417ecce5fd5dab95ec726da11d
Reviewed-on: https://bazel-review.googlesource.com/#/c/2690
MOS_MIGRATED_REVID=112446514
|
|
|
|
|
|
|
|
| |
$(...) is incorrect when doing a test to test the return value, (...)
should be used instead.
--
MOS_MIGRATED_REVID=110248027
|
|
|
|
|
|
|
| |
will get rid of all the "ghost flakes" where tests crashed with no apparant reason printed into our logs. Now a stack trace is printed and an easy to understand failure reason, too.
--
MOS_MIGRATED_REVID=110142957
|
|
|
|
|
|
|
| |
This allows ijar to process jars with >65535 entries.
--
MOS_MIGRATED_REVID=109321374
|
|
|
|
|
|
|
|
| |
As per discussion with Alan, just use the same copyright than
for the rest of Bazel and adds Alan as an author.
--
MOS_MIGRATED_REVID=108250408
|
|
|
|
|
|
|
|
| |
This doesn't change behaviour (they continue to get dropped from the interface
jar), but it avoids some spurious "skipping unknown attribute" warnings.
--
MOS_MIGRATED_REVID=105767979
|