github
/
jgit
mirror of https://gitee.com/github-mirror-repo/jgit.git
1
0
Fork 0
Code Issues Releases Wiki Activity
纯java实现的git操作库。
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5359 Commits
45 Branches
0 Tags
37 MiB
Tree: a3588cbb2a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a3588cbb2a'
${ noResults }
jgit/org.eclipse.jgit.junit/META-INF/MANIFEST.MF

39 lines
1.6 KiB
Raw Normal View History Unescape

Partial revert "Switch build to Apache Felix maven-bundle-plugin" This restores the ability to build using just Eclipse without strange procedures, extra plugins and it is again possible to work on both JGit and EGit in the same Eclipse workspace with ease. Change-Id: I0af08127d507fbce186f428f1cdeff280f0ddcda Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
15 years ago
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %plugin_name
Bundle-SymbolicName: org.eclipse.jgit.junit
JGit v4.9.1.201712030800-r Change-Id: I8bf477778c9dac41cb65233a9e7d590531a836b7 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
7 years ago
Bundle-Version: 4.9.1.201712030800-r
Partial revert "Switch build to Apache Felix maven-bundle-plugin" This restores the ability to build using just Eclipse without strange procedures, extra plugins and it is again possible to work on both JGit and EGit in the same Eclipse workspace with ease. Change-Id: I0af08127d507fbce186f428f1cdeff280f0ddcda Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
15 years ago
Bundle-Localization: plugin
Bundle-Vendor: %provider_name
Restore lazy Bundle-ActivationPolicy removed in 3a4a5a4e This header was removed unintentionally from some bundles in 3a4a5a4e57f41c595ba950ea6f6680260669bf34. Restore it to ensure lazy activation of bundles. Change-Id: I1f841f978fb93278e3ec0533a01f1363510dd976 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
9 years ago
Bundle-ActivationPolicy: lazy
Change JGit minimum execution environment to JavaSE-1.8 Bug: 500059 Change-Id: I47f3f6749a67da52029f84e002d9b155ed56d2b7 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
8 years ago
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Prepare 4.9.1-SNAPSHOT builds Change-Id: Ic49fd093d3fe4324c4d83aba74033040fcaa37a6 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
7 years ago
Import-Package: org.eclipse.jgit.api;version="[4.9.1,4.10.0)",
org.eclipse.jgit.api.errors;version="[4.9.1,4.10.0)",
org.eclipse.jgit.dircache;version="[4.9.1,4.10.0)",
org.eclipse.jgit.errors;version="[4.9.1,4.10.0)",
org.eclipse.jgit.internal.storage.file;version="[4.9.1,4.10.0)",
org.eclipse.jgit.internal.storage.pack;version="[4.9.1,4.10.0)",
org.eclipse.jgit.lib;version="[4.9.1,4.10.0)",
org.eclipse.jgit.merge;version="[4.9.1,4.10.0)",
org.eclipse.jgit.revwalk;version="[4.9.1,4.10.0)",
org.eclipse.jgit.storage.file;version="[4.9.1,4.10.0)",
org.eclipse.jgit.treewalk;version="[4.9.1,4.10.0)",
org.eclipse.jgit.treewalk.filter;version="[4.9.1,4.10.0)",
org.eclipse.jgit.util;version="[4.9.1,4.10.0)",
org.eclipse.jgit.util.io;version="[4.9.1,4.10.0)",
org.eclipse.jgit.util.time;version="[4.9.1,4.10.0)",
Add a RepeatRule to help repeating flaky tests A JUnit TestRule which enables to run the same JUnit test repeatedly. This may help to identify the root cause why a flaky tests which succeed most often does fail sometimes. Add the RepeatRule to the test class containing the test to be repeated: public class MyTest { @Rule public RepeatRule repeatRule = new RepeatRule(); ... } and annotate the test to be repeated with the @Repeat(n=<repetitions>) annotation: @Test @Repeat(n = 100) public void test() { ... } then this test will be repeated 100 times. If any test execution fails test repetition will be stopped. Change-Id: I7c49ccebe1cb00bcde6b002b522d95c13fd3a35e Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
9 years ago
org.junit;version="[4.0.0,5.0.0)",
org.junit.rules;version="[4.9.0,5.0.0)",
org.junit.runner;version="[4.0.0,5.0.0)",
org.junit.runners.model;version="[4.5.0,5.0.0)"
Prepare 4.9.1-SNAPSHOT builds Change-Id: Ic49fd093d3fe4324c4d83aba74033040fcaa37a6 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
7 years ago
Export-Package: org.eclipse.jgit.junit;version="4.9.1";
Update uses-clauses in OSGi manifests In Bug 476164 it was reported that EGit doesn't start when the platform comes with jsch 0.1.51 while this version of EGit/JGit brings jsch 0.1.53. This could be caused by outdated uses-clauses. Hence recompute them using PDE tooling. Bug: 476164 Change-Id: I185ba097884ead9cd034eba842bd3bf34181a99b Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
9 years ago
uses:="org.eclipse.jgit.dircache,
org.eclipse.jgit.lib,
org.eclipse.jgit.revwalk,
org.eclipse.jgit.internal.storage.file,
org.eclipse.jgit.treewalk,
org.eclipse.jgit.util,
org.eclipse.jgit.storage.file,
Define MonotonicClock interface for advanced timestamps MonotonicClock can be implemented to provide more certainity about time than the standard System.currentTimeMillis() can provide. This can be used by classes such as PersonIdent and Ketch to rely on more certainity about time moving in a strictly ascending order. Gerrit Code Review can also leverage this interface through its embedding of JGit and use MonotonicClock and ProposedTimestamp to provide stronger assurance that NoteDb time is moving forward. Change-Id: I1a3cbd49a39b150a0d49b36d572da113ca83a786
8 years ago
org.eclipse.jgit.api",
Prepare 4.9.1-SNAPSHOT builds Change-Id: Ic49fd093d3fe4324c4d83aba74033040fcaa37a6 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
7 years ago
org.eclipse.jgit.junit.time;version="4.9.1"