Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362376 - Support Hard-links for local project cloning
Summary: Support Hard-links for local project cloning
Status: NEW
Alias: None
Product: JGit
Classification: Technology
Component: JGit (show other bugs)
Version: 1.1   Edit
Hardware: All Unix All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-28 17:14 EDT by Roland Schulz CLA
Modified: 2013-03-19 01:22 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Schulz CLA 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 CLA 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 CLA 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 CLA 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 CLA 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 CLA 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.