This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | sftp: symbolic links are not preserved when uploading | ||
---|---|---|---|
Product: | contrib | Reporter: | geckoneer <geckoneer> |
Component: | RemoteFS | Assignee: | remotefs@contrib <remotefs> |
Status: | NEW --- | ||
Severity: | blocker | CC: | swilk, terje7601 |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
geckoneer
2009-09-03 19:40:53 UTC
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 symLink. 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. See http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.3.7 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. |