Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 311293

Summary:	Unable to Find Resource for jGit 0.7.1
Product:	[Technology] JGit	Reporter:	David Carver <d_a_carver>
Component:	JGit	Assignee:	Project Inbox <jgit.core-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	sop
Version:	0.7.1
Target Milestone:	0.8.0
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Carver

2010-05-01 16:59:32 EDT

I'm trying to follow the instructions on http://www.eclipse.org/jgit/download/ for referencing in a maven2 build the jGit repository and particularly 0.7.1.

I've noticed that the current Hudson git plugin is several versions behind on it's jGit usage, and I wanted to update it so that it uses the latest 0.7.1 version.   It appears when I run the maven build, it can't find the necessary POM file for 0.7.1, as I get the following information:

Downloading: http://download.eclipse.org/jgit/maven//org/eclipse/jgit/org.eclipse.jgit/0.7.1./org.eclipse.jgit-0.7.1..pom
[INFO] Unable to find resource 'org.eclipse.jgit:org.eclipse.jgit:pom:0.7.1.' in repository jgit-repository (http://download.eclipse.org/jgit/maven/)

Comment 1 David Carver

2010-05-01 17:00:37 EDT

I've also tried it as follows.

[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
Downloading: http://download.eclipse.org/jgit/maven/org/eclipse/jgit/org.eclipse.jgit/0.7.1./org.eclipse.jgit-0.7.1..pom
[INFO] Unable to find resource 'org.eclipse.jgit:org.eclipse.jgit:pom:0.7.1.' in repository jgit-repository (http://download.eclipse.org/jgit/maven/)

Comment 2 David Carver

2010-05-01 17:18:36 EDT

Hmmm...I might have this working now...looks like I had two dependencies in the pom.xml file and it was getting confused.

Comment 3 Shawn Pearce

2010-05-13 13:03:35 EDT

(In reply to comment #2)
> Hmmm...I might have this working now...looks like I had two dependencies in the
> pom.xml file and it was getting confused.

So we should close this bug?

Comment 4 David Carver

2010-05-13 13:19:17 EDT

Yes, marking as resolved Invalid.