Closed GoogleCodeExporter closed 8 years ago
EGit/JGit does not work with symlinks. It just seesn the content they point at.
The
reason is that Java does not support symlinks so support would require some for
some
native code, which we try to abstain from. Symlinks are not available on all
platforms, which makes it impossible to support on all platforms.
A number of workarounds are possible.
1) As msysgit does with and create a simple file with the link.
2) Cygwin approach and simulate using short cuts
3) As clearcase does and create copies of the linked files
4) Set the assume-unchanged flag and ignore them
5) An eclipse specific solution with a virtual file system
6) An eclipse specific solution involving linked resources.
None is high priority. I have worked with 3 using another SCM (guess) and that
"works"
sort of. A problem is that special operations will be needed to handle the
"symlinks"
on platforms that don't do symlinks.
Original comment by robin.ro...@gmail.com
on 3 May 2009 at 1:06
> EGit/JGit does not work with symlinks. It just seesn the content they point
at. The
> reason is that Java does not support symlinks so support would require some
for some
> native code, which we try to abstain from.
But that means that you effectively restrict Eclipse/EGit to *Java* *only*.
We are using EGit with RadRails (Eclipse derivative) and are working on a
Ruby/Rails project.
Since EGit breaks symlinks it also breaks our possiblity to work with EGit in
the real world.
If you do not really care whether the world outside can work with EGit then
setting the Prio of this bug to low is correct. If you do not want to ignore
the world outside Java then this bug has quite destructive consequences.
Original comment by tomas.po...@zhdk.ch
on 12 Jul 2010 at 11:25
See also discussion at http://www.eclipse.org/forums/index.php?t=tree&th=156013&
Original comment by tomas.po...@zhdk.ch
on 12 Jul 2010 at 11:36
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=300088 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=318598
They may not match the exact description, but the core issue is the same.
Original comment by robin.ro...@gmail.com
on 12 Jul 2010 at 4:45
Original issue reported on code.google.com by
chad...@gmail.com
on 23 Mar 2009 at 10:13