| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I1f5e98a5ed672e3a9c04ff82afd677282a663cb9
|
|\
| |
| |
| |
| |
| |
| | |
* stable-2.13:
Set version to 2.13.14
Change-Id: I502a32bd4ad31483c1675aae91709ef50e693cd3
|
| |
| |
| |
| | |
Change-Id: I6cbf560c895c1b20a02d3a61ca66b3e9e7af6100
|
| |
| |
| |
| |
| |
| | |
This will reduce conflicts when merging up to stable-2.15.
Change-Id: Ibcb0c8a8b42cbb383d48f642c62b70aa9de640c3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Upgrade the jna, slf4j and visible-assertions dependencies accordingly.
Do not upgrade commons-compress though, as this dependency brings too
many more ones in.
Change-Id: I4e8e5cf9f8cfef6c7702c29017cfaf1d9fa952ae
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This release fixes a regression that was introduced in the previous
release, where an infinite loop could occur when an object was not
found in the packfile and `core.trustfolderstat` was set to `false`.
Bug: Issue 10695
Change-Id: I11c1a5659f3d495fd78d3cdbc1733b816927a598
|
|\ \ \
| |/ /
|/| /
| |/
| |
| |
| | |
* stable-2.13:
Upgrade JGit to 4.5.7.201904151645-r
Change-Id: I54fe989b6b97cf260cee7c8f25daf00f1c108b2f
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This release fixes a regression that was introduced in the previous
release, where an infinite loop could occur when an object was not
found in the packfile and `core.trustfolderstat` was set to `false`.
Bug: Issue 10695
Change-Id: I39aaa2afff163bb74c90da748aac31f565a0bf90
|
| |
| |
| |
| | |
Change-Id: I570cc3fac62e030dfc47fa66e1c5350f989f098f
|
|\|
| |
| |
| |
| |
| |
| |
| |
| | |
* stable-2.13:
Bump Mina core to 2.0.16 and sshd to 1.4
Switch to java 8
Set version to 2.13.14-SNAPSHOT
Change-Id: Ie90c4735d183e14a34ee5eef5ae2151853018d09
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This release moves to Java 8 and fixes various bugs. See the sshd-core
release notes [1] and mina-project page [2] for details.
[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310849&version=12338322
[2] https://mina.apache.org/mina-project/
Change-Id: I5df8540fa96f91126ccd45446a070f2000436b15
|
| |
| |
| |
| |
| |
| |
| |
| | |
Official support for Java 7 was discontinued on April 2015: [1].
[1] https://www.java.com/en/download/faq/java_7.xml
Change-Id: I3aaf3eba118aaec3114a6dce8e93eda9dff4a18d
|
| |
| |
| |
| | |
Change-Id: I00d28da3df73f3396e124a1eb2b980c290ddf340
|
| |
| |
| |
| |
| | |
Change-Id: Ia25401b7d05085094ec3fa9db0b1fb8ac4ff9e0a
(cherry picked from commit aecbac85e20a4da735f58d3b24cea6b0b7e34cda)
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is a security update, see [1]
[1] https://github.com/bower/bower/releases
Change-Id: I1f471227831a4d257c829053b14c3a7370891f14
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Recent bazel version added an option to ensure, that tools are not used
in input, but instead passed as new parameter tools: [1].
Test Plan:
$ bazel build --incompatible_no_support_tools_in_action_inputs //...
[1] https://docs.bazel.build/versions/master/skylark/backward-compatibility.html#disallow-tools-in-action-inputs
Change-Id: I744ae1b28adac7d10037b445761c9dca771738bc
(cherry picked from commit 6af7e76bb26c6f5c64bfc02a5707a7f4478b33e7)
|
| |
| |
| |
| |
| |
| |
| |
| | |
This updates rules_closure to the version with Protobuf 3.7.1. The new
Protobuf version introduced dependency on zlib, that we also have to
add as transitive dependency.
Change-Id: Ic8fa455e86ed12dc3b7fe71ec2ba32ec00b043cd
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We want to include protobuf version upgrade to 3.7.0, that made Bazel
build of protobuf project forward compatible: [1].
[1] https://github.com/bazelbuild/rules_closure/pull/341
Change-Id: I1610c50a25d025833b34cec6b59da8395a32a67c
|
| |
| |
| |
| |
| |
| |
| |
| | |
As first noted in Ice22b3c23, HttpPluginModule is not appropriate to
extend because its configure method contains a bunch of bindings that
are specific to core; we're just lucky that it was harmless in practice.
Change-Id: I3b89150d18f41b164f350ff3f9649b9bc66880db
|
| |
| |
| |
| |
| |
| |
| | |
Before this change, the whole changes abandoning campaign aborted out of
the first failing abandon act encountered.
Change-Id: Ibe7ac031d8a987bf72c20c9c4d585c23b7c6117e
|
|\|
| |
| |
| |
| |
| |
| |
| |
| | |
* stable-2.13:
Set version to 2.13.13
Upgrade JGit to 4.5.6.201903121547-r
Consume JGit artifacts from Maven Central
Change-Id: I18ea1fd9ceaf158467ffbe6fe91685b67a70ce24
|
| |
| |
| |
| | |
Change-Id: Ib1aaca66f4f41d77b5ed7e84d5ef22ca110e2011
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Includes fixes for packfile list corruption during GC [1].
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=544199
Bug: Issue 10562
Change-Id: I6b1a6da355884f94b68cce5ab11f19d9d282017a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The recent JGit releases were published to the Eclipse repository
due to a security embargo. The embargo has since been lifted, and
the releases are available on Maven Central, so switch back to
consuming the artifacts from there.
This update was already done on the stable branches stable-2.9 to
stable-2.12 by change I054cc91f4, but was lost during the merge to
stable-2.13 in change Ib5243b6d2.
Change-Id: I55bbff5b0c738e9f419949d29b68b7cc88a748a7
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Ie5d579554f28047a51628cff2892fef065e6ee4d
|
|/ /
| |
| |
| | |
Change-Id: Iad5919940509269013355a171ceb7020a913e4c9
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Includes fixes for packfile list corruption during GC [1].
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=544199
Bug: Issue 10562
Change-Id: I7145601d5fe508c25c442008b1699432fefdccb5
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There were no breaking changes since the previously used version,
according to the release notes [1] and [2]. Considering the latter as
well since the former was just an overall Elastic stack version update
for Elasticsearch.
[1] https://www.elastic.co/guide/en/elasticsearch/reference/5.6/release-notes-5.6.15.html
[2] https://www.elastic.co/guide/en/elasticsearch/reference/5.6/release-notes-5.6.14.html
Change-Id: I7fe9f99265958f8d600c982e131134c3b5a484db
|
| |
| |
| |
| | |
Change-Id: Icae926a51377f295e7e420123ab989e1968f02e5
|
| |
| |
| |
| | |
Change-Id: I884dc7bd2900c73168eb48637f9964b27613c61e
|
| |
| |
| |
| |
| |
| |
| |
| | |
This new version has the nice feature of putting multiple chained method
calls before a .stream() on a single line. The diff is a bit large but
it's removing a lot of newlines which is nice.
Change-Id: I260b620aa6a1bc77b06be9672a1f281ab0d0d0f8
|
| |
| |
| |
| | |
Change-Id: I3b3d9321fe162597eb6fd8d40fc7340dd4dce74d
|
| |
| |
| |
| | |
Change-Id: If01f61085c9a9228e58101f941c4952590c8ad28
|
| |
| |
| |
| | |
Change-Id: I0ad36f82a2e6324e303205bccf8eaee2f3969952
|
| |
| |
| |
| | |
Change-Id: I159907dcdbbe23e50cfe1e7a1f50357576e0217e
|
| |
| |
| |
| | |
Change-Id: I71f1a96e34732fce1a165fbd0a3e19303ad5a3ed
|
| |
| |
| |
| |
| | |
Bug: Issue 10506
Change-Id: Ia42c69abaa755727756d1d2a44f972b15ea26b21
|
| |
| |
| |
| |
| |
| |
| |
| | |
This distinction is important as preparation for supporting Java 9,
and to be able to build Gerrit with Bazel 0.23.
Bug: Issue 10536
Change-Id: Ifee4ced92cc046aec65d39afa87437d895e0a8c7
|
| |
| |
| |
| | |
Change-Id: I0eb1533a85b4002af17cc355c7d20074861f6b31
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a JRE cannot be found at the location specified by JAVA_HOME or
container.javaHome, the server startup fails and an error message is
displayed.
Update the error message so that the reader realizes that while the
JAVA_HOME and/or container.javaHome might be *set* the value in them
might not be *valid*. An example of when this might be the case is when
the java installation was upgraded and the location changed from:
/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/jre
to:
/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home/jre
and while the JAVA_HOME environment variable got update to the new
location, container.javaHome did not and still pointed to the old (and
now invalid) location.
Change-Id: I24e0dc19781920e8901ef8743c847606ebd640ce
|
| |
| |
| |
| |
| |
| | |
Logging at INFO causes too much log spam.
Change-Id: I254bd8865bc6d880e8e1b6b491a8ce325021999a
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the constructor of the Args singleton, log the configured values
for reductionLimit and compileLimit.
In setPredicate, log the reduction limit that is actually used.
Change-Id: I300735ba4a7982de89337a5c179149023894acb6
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So far, if the name of the rule contained a dash (hyphen), as in
high-availability plugin for example, the test execution failed with
error message:
bazel-out/local-fastbuild/bin/high-availability_testsTestSuite.java:6:
error: '{' expected
public class high-availability_testsTestSuite {}
^
This is due to the fact that dashes are not valid characters in the name
of a Java class.
Workaround this by replacing any dash with an underscore.
Change-Id: I80fd4c5bcff0d2af6f337636bd942f30d6a521c6
|
| |
| |
| |
| | |
Change-Id: I4b7c4abd446f243b50e21875969f7651973bbceb
|
| |
| |
| |
| | |
Change-Id: I37d947d5ce0bc4be88101f9584428453dc8f492a
|
| |
| |
| |
| | |
Change-Id: I4e7c826914cd4da9043fb56e28523ea6b15be9c6
|
|\ \ |
|