aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/java_tools
Commit message (Collapse)AuthorAge
* Remove some left over bits of Java 7 supportGravatar Liam Miller-Cushon2017-09-04
| | | | | Change-Id: I3fce66ec2e63d152aafc0cf9ea067d6dbf1245f7 PiperOrigin-RevId: 167484075
* Split "shell", "graph" into their own packages.Gravatar philwo2017-08-29
| | | | PiperOrigin-RevId: 166849610
* This change adds an explicit dependency on the current Java runtime that ↵Gravatar lberki2017-08-28
| | | | | | | | indirectly depend on it by using the $(JAVABASE) or $(JAVA) Make variables. It was tested by running "bazel build --nobuild" on the affected targest to make sure that they still work. PiperOrigin-RevId: 166695324
* Auto-generate BUILD files for src/java_tools/junitrunnerGravatar ulfjack2017-08-28
| | | | | | | | | This and further changes may contain minor modifications to BUILD files that don't serve any apparent purpose. The reason for these changes is that we're switching from checked-in BUILD files to generated BUILD files, and there may be small differences between these files. PiperOrigin-RevId: 166684362
* REDACTEDGravatar Googler2017-08-17
| | | | PiperOrigin-RevId: 165439218
* Update JacocoCoverageRunnerGravatar elenairina2017-08-14
| | | | | | | new blaze Java implementation sends the runtime jars encapsulated in a metadata txt file, instead of listing them in the environment variable. The previous approach led to blaze crashing with an "Argument list too long" error. PiperOrigin-RevId: 165155269
* Internal changeGravatar Googler2017-08-14
| | | | PiperOrigin-RevId: 165003777
* Rewrite junitrunner integration testsGravatar ulfjack2017-08-11
| | | | | | | | | | | | Use $(location) to get the unittest.bash script, which allows this test to also run with a different label prefix. This involves removing the intermediate testenv.sh script, which doesn't seem to add much value. We might want to consider a sh_unit_test rule or macro that has an implicit dependency on the unittest.bash script and doesn't require every test to do this manually. PiperOrigin-RevId: 164846477
* Trigger a gc after processing a workrequest.Gravatar Googler2017-08-09
| | | | | RELNOTES: none PiperOrigin-RevId: 164667144
* Rearrange the java-langtools / javac-bootclasspath scriptsGravatar ulfjack2017-08-07
| | | | PiperOrigin-RevId: 164446300
* sed: fall back to -r if -E does not workGravatar ulfjack2017-08-04
| | | | PiperOrigin-RevId: 164252615
* Remove dependency on Apache common langGravatar ulfjack2017-08-02
| | | | PiperOrigin-RevId: 163840258
* Fix UNIX linker detection (was erroneously disabling ld.gold)Gravatar Allen Lavoie2017-08-01
| | | | | | | | | | Adds back a compiler test empty .cc file. Seems to be an omission in https://github.com/bazelbuild/bazel/commit/65cda4f219e564ccb190b2992151658dfae9904 The _is_gold_supported check in unix_cc_configure.bzl always fails without this change, since the file it's checking with isn't created. Looks like there may be other effects through _add_option_if_supported, although I only noticed because apparently I have written linker-specific code. Closes #3484. PiperOrigin-RevId: 163832465
* Auto-generate BUILD files for src/java_tools/singlejarGravatar ulfjack2017-07-31
| | | | | | | | | This and further changes may contain minor modifications to BUILD files that don't serve any apparent purpose. The reason for these changes is that we're switching from checked-in BUILD files to generated BUILD files, and there may be small differences between these files. PiperOrigin-RevId: 163525889
* Update jacoco coverage runner to consider some edge cases.Gravatar elenairina2017-07-19
| | | | | | | | | | After running the new coverage implementation on some real targets I found the following. 1. Inner classes with the same name could be added from different jars. Addressed this by analyzing classes with the same name exactly once. 2. Auto-generated files were added to the coverage report. This is resolved first on the blaze/bazel side by adding to the files with the exec paths of the instrumented files only those that are source files and on the coverage runner side by discarding all the files that are not in that file. PiperOrigin-RevId: 162478894
* Prepare JavaBuilder classloader masking for Java9Gravatar cushon2017-07-18
| | | | PiperOrigin-RevId: 162263240
* Change Test Runner to work with the new Bazel coverage implementation.Gravatar elenairina2017-07-14
| | | | | | | | | | The new implementation doesn't use one metadata jar for the whole build anymore, but wraps all the uninstrumented classes in each of the build jars, among with a txt file that contains the paths of the files to be instrumented. The paths will be used to output the entire relative filepath to the partial coverage report. Instead of one metadata jar containing all uninstrumented classes on the runtime classpath, the coverage runner will retrieve all the build jars on the runtime classpath. Because the build jars contain now both classes and uninstrumented classes, the coverage runner will not analyze the entire given jar, but only the classes in the given jars that have the right suffix. PiperOrigin-RevId: 161951370
* Fix build failure with old OS X mktempGravatar ilovezfs2017-07-14
| | | | | | | | | | | | This fixes a minor regression introduced by bazelbuild/bazel@2c3c87fab48646167e4233f539540df6b5ed3d04. mktemp's interface changed in OS X 10.11 to allow the prefix to be unspecified, but not specifying the prefix will cause the command to error out on OS X 10.10 and earlier. Closes #3281. PiperOrigin-RevId: 161805877
* Remove hard-coded -Xbootclasspath/p flags for javac and turbine invocationsGravatar cushon2017-07-12
| | | | | | | | And instead rely on the flags being set in java_toolchain.jvm_opts. This change is being made in preparation for JDK 9, which replaces -Xbootclasspath/p with --patch-module. PiperOrigin-RevId: 161620182
* Change JavaBuilder to work with the new Bazel Java coverage.Gravatar elenairina2017-07-11
| | | | | | The new implementation doesn't use the metadata jar anymore, but wraps all the uninstrumented classes in the build jar among with a txt file that contains the paths of the files to be instrumented. PiperOrigin-RevId: 161499019
* Remove support for -extra_checks:offGravatar cushon2017-07-07
| | | | | | | | | | it has been replaced by -XepDisableAllChecks, which disables all Error Prone checks instead of disabling the plugin. Disabling the plugin entirely breaks handling of other -Xep flags. RELNOTES[INC]: -extra_checks:off is no longer supported; use -XepDisableAllChecks instead PiperOrigin-RevId: 161127522
* Tweak buildjar/JavaBuilder to not output missing deps twice.Gravatar Googler2017-07-07
| | | | PiperOrigin-RevId: 161127284
* Automated rollback of commit ce7c4deda60a307bba5f0c9421738e2a375cf44e.Gravatar cushon2017-06-20
| | | | | | | | | | | | *** Reason for rollback *** See bazelbuild/bazel#3172 *** Original change description *** Add an experimental flag to Turbine to indicate to annotation processors that they are running in hjar compilation PiperOrigin-RevId: 159585343
* Update BUILD filesGravatar Ulf Adams2017-06-13
| | | | | | | | | | | We're currently maintaining two sets of BUILD files; one at Google, and one in the Git repository. We'd like to not do that. This change makes some of the Bazel BUILD files more closely match their counterparts, in preparation for removing the internal ones. Closes #3094. PiperOrigin-RevId: 158820490
* protobuf: Use bazel's native java_proto_library rules.Gravatar Jakob Buchgraber2017-06-06
| | | | | | | | | Additional changes: - Introduce a Skylark macro java_library_srcs that provides the source jars of a java_*_library rule. - Remove bazel's own java_proto_library implementation. Change-Id: I18f2259bc75ca0fb32dcd8a6a857c609bd2c7773 PiperOrigin-RevId: 158146210
* Migrate all tests to Truth (except the ones in the examples).Gravatar lberki2017-05-31
| | | | | RELNOTES: None. PiperOrigin-RevId: 157576492
* Optionally skip fallback to javac-turbineGravatar cushon2017-05-31
| | | | PiperOrigin-RevId: 157494773
* Migrate Java tests to Truth.Gravatar lberki2017-05-30
| | | | | | RELNOTES: None. PiperOrigin-RevId: 157446717
* Remove resourcejar handling from buildjarGravatar cushon2017-05-19
| | | | | | | singlejar is now used to add resources to library jars, so this code is unnecessary. PiperOrigin-RevId: 156473371
* Pass the platform classpath entries through to strict depsGravatar cushon2017-05-17
| | | | | | | from JavaBuilder's command line flags, instead of retrieving them using a non-standard filemanager API. PiperOrigin-RevId: 156226725
* Split classpaths more eagerlyGravatar cushon2017-05-15
| | | | | | | | | | Allow classpath command line options to be whitespace-separated, and store as lists instead of joined strings. This avoids some unnecessary string operations, and keeps command lines below the per-arg limit. A future change will update Bazel to pass unjoined classpaths. PiperOrigin-RevId: 156085128
* Re-enabling passing -sourcepath via javacopts.Gravatar elenairina2017-05-11
| | | | | | | This is needed until java_common.compile will be strong enough to replace java_library, exposing all its features. PiperOrigin-RevId: 155773169
* Avoid windows-incompatible absolute path syntaxGravatar cushon2017-05-11
| | | | | | See #2977 PiperOrigin-RevId: 155711073
* Migrate off versioned javac and Error Prone targetsGravatar Liam Miller-Cushon2017-05-09
| | | | | Change-Id: Iad1e07ad55d5304d7c3dbb8bdab856728a91432d PiperOrigin-RevId: 155375893
* Enable jarjar-ing the Jacoco deploy jar on every supported platform.Gravatar lberki2017-05-08
| | | | | | | The bugs that broke this on Windows ( https://github.com/bazelbuild/bazel/issues/2306 and https://github.com/bazelbuild/bazel/issues/2342 ) have been fixed and FreeBSD has been bootstrapped so we can do this there, too. RELNOTES: None. PiperOrigin-RevId: 155371373
* Use the Java version of singlejar for building the Jacoco coverage runner ↵Gravatar lberki2017-05-08
| | | | | | | | | deploy jar. I thought that didn't work for some reason, but I apparently made a mistake while writing the command line. RELNOTES: None. PiperOrigin-RevId: 155368830
* More windows conditionsGravatar dmarting2017-05-05
| | | | | | | | https://github.com/bazelbuild/bazel/commit/610bf143dd02020e6cd5c94db38ff54c5a504b12 forgot to add them in the tools selection so we were still building C++ singlejar on Windows MSVC where we cannot bootstrap it. PiperOrigin-RevId: 155219067
* Add more condition for the windows platformGravatar dmarting2017-05-05
| | | | | | With MSYS-less version of Bazel for Windows, we have several config settings that correspond to windows, list them all in the select (right now it is breaking our CI: http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=windows-msvc-x86_64/1477/) PiperOrigin-RevId: 155211130
* Make JacocoCoverage_deploy.jar deterministic by running the output of jarjar ↵Gravatar lberki2017-05-05
| | | | | | | | | through `singlejar --normalize`. Fixes #2912. RELNOTES: None. PiperOrigin-RevId: 155193074
* Add a javac-turbine option for the reduced classpath optimizationGravatar cushon2017-05-04
| | | | PiperOrigin-RevId: 155131707
* Clean VanillaJavaBuilder output directoriesGravatar cushon2017-05-04
| | | | | | | | | | to ensure outputs from any previous local builds are discarded. To cherry-pick for #2692. Fixes #2941 PiperOrigin-RevId: 155089391
* JavaBuilder accepts a new --testonly argument to mark compilations ofGravatar eaftan2017-04-27
| | | | | | | test code. Error Prone will use these to distinguish between test and production code, e.g. for enforcing @VisibleForTesting. PiperOrigin-RevId: 154370318
* Prepend javac to test bootclasspathGravatar cushon2017-04-25
| | | | PiperOrigin-RevId: 154098929
* Update to javac9-r4023Gravatar cushon2017-04-25
| | | | PiperOrigin-RevId: 154078281
* Embed a prebuilt jarjar into Bazel so that Android builds work again.Gravatar lberki2017-04-20
| | | | | | | Fixes #2848. RELNOTES: None. PiperOrigin-RevId: 153692641
* Re-enable the Java coverage tests.Gravatar lberki2017-04-18
| | | | | | | | | It has been disabled in https://github.com/bazelbuild/bazel/commit/bce889840f91f14c05418d960984bcf1a5f59411 and in https://github.com/bazelbuild/bazel/commit/21fb8cac60c36cb527d6131ab0092bcdf138d99a and then was not re-enabled. Also update src/java_tools/junitrunner/java/com/google/testing/coverage/BUILD to which I accidentally submitted a change directly to our OSS repository. RELNOTES: None. PiperOrigin-RevId: 153460778
* Simplify LocalSpawnRunnerGravatar ulfjack2017-04-18
| | | | PiperOrigin-RevId: 153444516
* Vendor jarjar instead of using a binary version of it.Gravatar Lukacs T. Berki2017-04-18
| | | | | | | | | | | | | | | It appears that jarjar is not actually used except for renaming classes in the coverage collecting Java test runner as verified by `find . -name BUILD | xargs grep jarjar` Yak shaving for #2820. This is necessary because the current version of jarjar does not work with Java 8 classes because it embeds a version of ASM that doesn't support that yet. Change-Id: I6ac59b84bbbc1e85fe8e7f4f4876b98fc6129df0
* Roll forward of ↵Gravatar cushon2017-04-18
| | | | | | | | https://github.com/bazelbuild/bazel/commit/4a303e2cd840810b95cbc793e38bdca48e6d9556 Only unescape @@-quoted args once PiperOrigin-RevId: 153189611
* Automated g4 rollback of commit b0ac3b41700cdc575c36ff2de191bc9ba2b6abf0.Gravatar cushon2017-04-14
| | | | | | | | | | | | | | | | | | *** Reason for rollback *** kokoro failures were not flakes :( *** Original change description *** Fix escaping of '@' in javabuilder command lines "@" is used to denote params files, so when it appears in labels it is escaped as "@@". The second "@" should be removed during flag parsing to avoid e.g. having it show up in strict deps errors. See bazelbuild/buildtools#83 PiperOrigin-RevId: 153127997
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-04 21:13:04 +0000