I have a remote Linux server and locally Windows XP. Some of the files on the server are actually symbolic links which
point to other files.
When I edit these files and upload (for example, with "upload on save" feature turned on) symbolic link is removed and
"normal" file is created.
The normal behavior would be to preserve the symbolic link on the remote side and change the actual file. Note that
there may be several links in a chain :)
Also, on Windows Vista and later it would be great to create symbolic links locally when making a download action (if
they point to the file which is within the locally accessible tree). An option how to handle the symbolic links would
also be great.
Confirmed for 6.8 M2.
Have increased priority as this is a destructive bug that is deleting the original file system structure.
When the editor downloads a filesytem, then uploads it again, it treats symlinks as files or folders instead of
retaining the knowledge that they were symlinks.
Additionally, netbeans is also failing on the following structure
/home/user/public_html/symLinkedFolder -> /home/anotherFolder/symLinkDestination
if Netbeans has access to public_html then it fails to download the symlink "symLinkedFolder".
I'd say this is probably related to the fact that the IDE is downloading a symlink as a file/folder instead of as a
It gets even worse. When you just download the sources from the remote server, NetBeans will perform some kind of two way synchronization. So your symlinks will be destroyed by just downloading the sources.
I can confirm this behavior still exists in 7.0 beta 2
It would be great if this feature were aware of svn property "svn:special". This property is set on symbolic links which came from svn repository, so it would be possible to recreate the symbolic link o remote file system based on the content of the checked out / updated symlink.
I can confirm symlinks are not working correctly for SFTP on Netbeans 7.1 final on Mac OS X Lion.
One of the projects I work on has a symlink to an external library that is outside of the code base. The destination of that symlink does not exist on my workstation, but does exist on production and development servers. So, rather than changing my symlink to a normal file containing the destination of the symlink, the symlink is being deleted completely.