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

Bug 362376

Summary:	Support Hard-links for local project cloning
Product:	[Technology] JGit	Reporter:	Roland Schulz <roland>
Component:	JGit	Assignee:	Project Inbox <jgit.core-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	caniszczyk, matthias.sohn, remy.suen, thomas
Version:	1.1
Target Milestone:	---
Hardware:	All
OS:	Unix All
Whiteboard:

Description Roland Schulz

2011-10-28 17:14:28 EDT

Hard-link support has been discussed on the mailing list before:
http://dev.eclipse.org/mhonarc/lists/egit-dev/msg00341.html

Shawn mentioned that JNA-Posix cannot be used because of the GPL license. It is now available under tri-license LPGL/GPL/CPL. Would it be now be possible to use it for JGit?

Comment 1 Remy Suen

2011-10-28 18:26:53 EDT

If it's the Common Public License then it should be possible from what I understand.

Comment 2 Chris Aniszczyk

2011-10-28 18:28:33 EDT

Doesn't Java7 support this now via java.nio.file.Files.createLink(...)

I would rather go that route.

Comment 3 Roland Schulz

2011-10-28 18:41:27 EDT

Yes. But I would think that you don't want to require Java7 for Juno. So until Java7 is required, JNA might be the best option.

Comment 4 Chris Aniszczyk

2011-10-28 18:47:50 EDT

I rather use Java7 if available otherwise degrade gracefully. It's a bit of a pain to get third party libraries through the IP process at eclipse.org :)

Comment 5 Thomas Hallgren

2013-03-19 01:22:21 EDT

I'm with Chris on this one. Not because of licensing but because JGit is pure-java. Introduce JNA and you introduce platform dependencies with it and one of the major reasons for JGits existence is gone. I mean, going that route, why not create a JNI layer for the native Git client instead? Much less maintenance.