The Polymer 3 doesn't support HTML import. To avoid massive code
changes during transition to Polymer 3 bridges must be added.
Bridges are added as a git submodule.
The bridges are not used in this change.
Change-Id: I3989a303e44dad75fa286228bf510e72b06aae91
The branch value is only used by Gerrit to manage automatic
submodule subscription updates. This feature is not used for
the jgit submodule because its code is reviewed on another
gerrit server.
Change-Id: I65594a64fbe4715baf1351a5c8b64af3618366fb
This is the second attempt to build JGit from the source using git
submodule approach. The first attempt that was abandoned is here: [1].
Using a submodule to bring in the source files vastly simplifies
updating JGit. Gerrit developers can bump the SHA-1 of the submodule
and not deal with the Maven rebuild process for JGit.
This change updates JGit dependency from 5.4.3.201909031940-r to commit
009e07882fee2b0ad2ebe7ba44e2ff52c101f858, and Javadoc version from:
5.4.3.201909031940-r to 5.5.0.201909110433-r.
To bump to new Javadoc API _DOC_VERS should be updated in
java/com/google/gerrit/extensions/BUILD to point to the desired JGit
Javadoc release.
JGit sources are imported in Eclipse as source folders. One side effect
of this change is that the source code warnings for JGit project are now
shown.
[1] https://gerrit-review.googlesource.com/c/gerrit/+/61892
Feature: Issue 11737
Change-Id: I16370e57f27e26b2382243ca448484f53dfa96bb
Having a mechanism to discover, install and upgrade plugins
is an expected feature for a core distribution.
Plugin manager has been included since the very beginning in
the binary packages (RPMs and Debs) and in the famous Docker
image that has been pulled over 100k times.
The only place where the plugin-manager is not present is
the WAR package: this proposal fills the gap and aligns the
package with the rest of the current distributions.
Feature: Issue 10717
Change-Id: Ia5b9c74f177aac135100d3cf138a38697a2db0ca
Also add dependency on Mockito, which is now exported in the
acceptance framework. There are several other plugins using
this dependency, so exporting it in the acceptance framework
will have the nice side effect that we no longer need to keep
updating them individually.
Also note that one of the other plugins that uses Mockito is
the webhooks plugin, which is also planned to be added as a
core plugin.
Feature: Issue 8863
Change-Id: I72c0694ec6fcbabc2ef030014268738aa69cb707
The cookbook-plugin was made read-only with the intention of replacing
it with a new examples plugin.
Remove the submodule before any futher changes are made in core Gerrit
that will end up causing build problems due to interface changes.
Change-Id: Id8536dc9c3750eecd76bdf61e1d24af92333ce25
Like the cookbook plugin, keep the singleusergroup plugin in the
primary build to make it easier to detect API version changes,
but do not (yet) include it as a core plugin in release binaries.
Change-Id: I24d2d3c7eb461d573d1666a1af631a3caeee2eac
In 246f9b52854fc1b11dbe14085e2c0ac0f6ddda95 the submodules were
changed to use absolute paths, to prevent problems on mirrors
where only the gerrit project is present, or where the plugin gits
are not on the same relative path as they are on gerrit-review.
This however causes problems for mirrors where the plugins *are*
present and in the expected relative path: the plugins are still
cloned off the gerrit-review server, rather than the mirror.
Switch them back to relative paths to fix this.
Change-Id: I30b5e6f96fbbc538665be9a618c3cf092e1588f1
The helloworld plugin is used to demonstrate features of the
plugin API.
Add it as a submodule so it's included in the tree. Thus we
can make sure it's always buildable against the latest Gerrit
code base.
Change-Id: I1450ce02d04cf213eaeaaca0386a357d99423c4a
While the use of relative Urls for referencing included plugin
repositories works nicely when cloning directly from gerrit-review, it
caused problems when cloning from a mirror that only mirrored the main
gerrit repository. There 'git submodule update' did not work unless
the referenced plugin repositories were also mirrored in exactly the
same relative position as on gerrit-review. Hence, we switch to
referencing the included plugin repositories by absolute Urls.
Change-Id: I1230f398cc7d2323922aff7f7acf92eac30f3ab5
Require the core plugins whenever a Gerrit build is run.
These are pulled into the Maven Reactor by being inside
of git submodules. Plugins can be omitted by passing a
-Dgerrit.plugins.skip=true flag on the command line.
Change-Id: I7246389bcae9e98d5f1d46208ff515855eb7c474