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.
1477 Commits
45 Branches
0 Tags
37 MiB
Tree: 6ec6169215
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6ec6169215'
${ noResults }
jgit/org.eclipse.jgit.http.test/META-INF/MANIFEST.MF

40 lines
1.8 KiB
Raw Normal View History Unescape

Make HTTP test project work in Eclipse The Jetty components are not available as part of Eclipse, but a P2 packaged version can be found via [1] for Eclipse 3.5 and newer. [1] http://wiki.eclipse.org/Jetty-OSGi_SDK Change-Id: Ibd5930bb9fc9589125876ca50c52e58bd31b051c Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
15 years ago
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Correct bundle, provider names to be consistent Technically our project name is "JGit", not "Java Git". In fact there is already another project called "JavaGit" (no space) that we don't want to become confused with. Ensure we always call ourselves "JGit" in user visible assets, like the bundle name. Other Eclipse products list their provider as "Eclipse.org", not "eclipse.org". So list ourselves that way in all of our plugin.properties files. Change-Id: Ibcea1cd6dda2af757a8584099619fc23b7779a84 Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
15 years ago
Bundle-Name: %plugin_name
Make HTTP test project work in Eclipse The Jetty components are not available as part of Eclipse, but a P2 packaged version can be found via [1] for Eclipse 3.5 and newer. [1] http://wiki.eclipse.org/Jetty-OSGi_SDK Change-Id: Ibd5930bb9fc9589125876ca50c52e58bd31b051c Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
15 years ago
Bundle-SymbolicName: org.eclipse.jgit.http.test
Qualify post-0.12 builds Change-Id: I70fe2671321efb5c3d271121ce00299533d1b388 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
14 years ago
Bundle-Version: 1.0.0.qualifier
Correct bundle, provider names to be consistent Technically our project name is "JGit", not "Java Git". In fact there is already another project called "JavaGit" (no space) that we don't want to become confused with. Ensure we always call ourselves "JGit" in user visible assets, like the bundle name. Other Eclipse products list their provider as "Eclipse.org", not "eclipse.org". So list ourselves that way in all of our plugin.properties files. Change-Id: Ibcea1cd6dda2af757a8584099619fc23b7779a84 Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
15 years ago
Bundle-Vendor: %provider_name
Bundle-Localization: plugin
Make HTTP test project work in Eclipse The Jetty components are not available as part of Eclipse, but a P2 packaged version can be found via [1] for Eclipse 3.5 and newer. [1] http://wiki.eclipse.org/Jetty-OSGi_SDK Change-Id: Ibd5930bb9fc9589125876ca50c52e58bd31b051c Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
15 years ago
Bundle-RequiredExecutionEnvironment: J2SE-1.5
Cleanup OSGi Import-Package specifications to use versions Actually set the range of versions we are willing to accept for each package we import, lest we import something in the future that isn't compatible with our needs. Change-Id: I25dbbb9eaabe852631b677e0c608792b3ed97532 Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
15 years ago
Import-Package: javax.servlet;version="[2.5.0,3.0.0)",
javax.servlet.http;version="[2.5.0,3.0.0)",
JGit Build: use jetty 7.1.6 Jetty 7.1.6 is used because this version is also available in P2. Change-Id: I410fbca8592cac6e58c651c4d086573820e777a5 Signed-off-by: Jens Baumgart <jens.baumgart@sap.com>
14 years ago
org.eclipse.jetty.continuation;version="[7.1.0,8.0.0)",
org.eclipse.jetty.http;version="[7.1.0,8.0.0)",
org.eclipse.jetty.http.security;version="[7.1.0,8.0.0)",
org.eclipse.jetty.io;version="[7.1.0,8.0.0)",
org.eclipse.jetty.security;version="[7.1.0,8.0.0)",
org.eclipse.jetty.security.authentication;version="[7.1.0,8.0.0)",
org.eclipse.jetty.server;version="[7.1.0,8.0.0)",
org.eclipse.jetty.server.handler;version="[7.1.0,8.0.0)",
org.eclipse.jetty.server.nio;version="[7.1.0,8.0.0)",
org.eclipse.jetty.servlet;version="[7.1.0,8.0.0)",
org.eclipse.jetty.util.component;version="[7.1.0,8.0.0)",
org.eclipse.jetty.util.log;version="[7.1.0,8.0.0)",
org.eclipse.jetty.util.thread;version="[7.1.0,8.0.0)",
Qualify post-0.12 builds Change-Id: I70fe2671321efb5c3d271121ce00299533d1b388 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
14 years ago
org.eclipse.jgit;version="[1.0.0,1.1.0)",
org.eclipse.jgit.errors;version="[1.0.0,1.1.0)",
org.eclipse.jgit.http.server;version="[1.0.0,1.1.0)",
org.eclipse.jgit.http.server.glue;version="[1.0.0,1.1.0)",
org.eclipse.jgit.http.server.resolver;version="[1.0.0,1.1.0)",
org.eclipse.jgit.junit;version="[1.0.0,1.1.0)",
org.eclipse.jgit.lib;version="[1.0.0,1.1.0)",
org.eclipse.jgit.nls;version="[1.0.0,1.1.0)",
org.eclipse.jgit.revwalk;version="[1.0.0,1.1.0)",
org.eclipse.jgit.storage.file;version="[1.0.0,1.1.0)",
org.eclipse.jgit.transport;version="[1.0.0,1.1.0)",
org.eclipse.jgit.transport.resolver;version="[1.0.0,1.1.0)",
org.eclipse.jgit.util;version="[1.0.0,1.1.0)",
org.eclipse.jgit.junit.http;version="[1.0.0,1.1.0)",
Require the hamcrest packaging that comes with Eclipse The other one gets installed with SWTBot, but you do not need it if you do not hack EGit. Using import-package instead of require-bundle fixes the dependency. Actually we do not need hamcrest at this time, but JUnit wants it. Change-Id: I59873618f86d02e8439d40c1f322ea8e5c4fe3fc Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
14 years ago
org.junit;version="[4.0.0,5.0.0)",
org.hamcrest.core;version="[1.1.0,2.0.0)"