Jetty 9 was built with compiler settings producing class files that
are not recognized by Java 6 runtimes.
Gerrit 2.9 will require Java 7 as its minimum runtime version.
Change-Id: Ifed3f9e07bf77a7a737b16c20e6e400acd990649
JGit cannot currently run GC on DFS backed repositories. Only offer
GC if the implementation of GitRepositoryManager is the default
LocalDiskRepositoryManager, which uses FileRepository, a type JGit
knows how to run GC on.
Change-Id: I23df492cb9657ca7bb5190b5313d2e62cdd87df4
AsciiDoctor have different understanding of [verse] with asciidoc, causing some
rendering differences. To get similar result with asciidoc, we use something
else instead of [verse] now.
Screenshots:
before:
http://imgur.com/JKMdBiv
after:
http://imgur.com/yFVvVac
Change-Id: I14e84f0e998e1e87b633681e8028ad657bde07e4
CodeMirror finally supports hiding the first line completely, revise
SkipBar implementation to be less hackish.
While we now use horizontal scrolling, line widgets (SkipBars and
CommentBoxes) should not scroll with the content. Set "noHScroll"
to true when creating them.
Remove clipping when calling scrollTo() since CodeMirror now handles that.
Change-Id: I0c08597bb1c856b332fe96fa700fea0a68504c9a
With this UI actions can create a drop-down-list from JavaScript by
var s = c.select(['VALUE1', 'VALUE2', 'VALUE3', 'VALUE4'], 2);
with having 'VALUE3' preselected.
The selected value can be retrieved by
c.selected(s)
Change-Id: I6ff135c313fd173909d6cf87f96a90e0ceb50d46
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
This changes extends gerrit_plugin function with additional gwt_module
parameters. When passed, GWT application is created. Assumtion is met,
that this application depends on gerrit-plugin-gwtui module.
With this change Gerrit GWT plugins can be build with Buck:
MODULE = 'com.googlesource.gerrit.plugins.cookbook.HelloForm'
gerrit_plugin(
name = 'cookbook-plugin',
srcs = glob(['src/main/java/**/*.java']),
resources = glob(['src/main/**/*']),
gwt_module = MODULE,
manifest_entries = [
'Gerrit-PluginName: cookbook',
'Gerrit-Module: com.googlesource.gerrit.plugins.cookbook.Module',
'Gerrit-HttpModule: com.googlesource.gerrit.plugins.cookbook.HttpModule',
'Gerrit-SshModule: com.googlesource.gerrit.plugins.cookbook.SshModule',
]
)
Change-Id: I4b131c7c2672675d99457651fcee63bf4f149c2f
New version has features which be useful for Gerrit core and plugins:
* new hidden attribute, specifying to hide it in help message
* new depends attribute, specifying the dependent option(s)
* multiValued attribute was removed
Change-Id: Ic7e9f37231cb83940db50fe3b9efe8ad972108cf
By default progress information on GC is not shown anymore. The
progress information is not useful if the command output should be
parsed by scripts or if it should be shown in the UI. Add new option
was added so that the progress information can be switched on.
Change-Id: I9d7d04f4e2666002dc9de05764e010d052d964e8
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
Do not navigate to the project list. After a project action users
expect to stay on the project screen.
Change-Id: I37fcb80a837f5c27810ecdf21dfa444aa2fb6d23
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
Wrap the result in a NativeString, and naively cast it to whatever
the callback is asking for (which is not particularly less safe than
what we do for JSON).
Change-Id: I1807ce33544964533f8d2a88c45576c18f4394ec
It is much cheaper to check READ access on a ref than to check
if a commit is merged into that ref. Therefore, do the checks in
this order and avoid traversal of potentially large commit graph
when we know that the user cannot read that branch.
Change-Id: I008990915e15854100a84b3d795f6c54efe35c81
* stable-2.8:
Fix: Performance issue when traversing large Git repositories
Add release notes for recently made changes
Linkify starred change state documentation
Update release notes with recently made changes
Change-Id: I21cc559018eff24353ba2a1698036858791fa517
The commit:
3488eece9f1a197aedfe41d0b3275065c4981c82
"Verify access to source ref during add branch operation"
introduced a performance issue on Git repositories with
many refs and large commit graphs. Tree traversal,
to verify visibility of initial revision, included namespaces
whose tips are not reachable from any branch. Iterating over
all these refs ended up stalling our system.
By filtering the refs, so that only "refs/heads" and "refs/tags"
namespaces are traversed, time was reduced from 1h+ to ~10 seconds
for a create branch operation.
Change-Id: I64c1123cc092fa5a7de6db8be7999672bd9f67b0
So far the 'conflicts:<change>' query operator returns all changes that
touch at least one file that was also modified by the specified change.
This means all changes that potentially conflict with the specifed
change are returned.
Now we check the mergeability for the changes and only return those
changes that actually conflict. This means now the 'Automatically
resolve conflicts' project setting is taken into account and if the
content merge succeeds a change is not returned.
A new persistent cache is added to cache for two commits and a given
submit type whether the commits are conflicting. This ensures that the
expensive mergeability check for two changes is only done once.
Change-Id: I1d6a3c431ed679f786e589bbed3aed52fe439895
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
