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.
A user complained that when running a project, no data files are uploaded to the remote (you can see details in CND user forum, the topic is "Need Data File for C/C++ Remote Run"). This concerns "Auto Copy" mode only.
*** Bug 186397 has been marked as a duplicate of this bug. ***
When fixing, unit tests should be taken into consideration.
1) There is a "Download to" menu item 2) With SFTP mode, the problem does not exist at all
Valdimir, The automatic copying happens only when one chooses "Automatic copying". Any other mode forces us to manually copy the files using "upload to <remote host" before initiating a compilation on the remote host. Selecting anything other than "Automatic copying" does not allow the files to be copied automatically. We should be able to push the files without selecting anything in the menu when we build. I think the design of development in Netbeans allows us to build simply by clicking "Build" in the right click menu of the project. The click on "Build" copies the files (new/changed) on to the remote host (if not already copied) and initiates a build on the remote host. The problem is that when the automatic mode is select some of the files that are transferred to the remote hosts have the contents replaced by nulls.
I'd just like to give this a bump, since it's still a bug as of 8.0.2 under Automatic Copying. Source files that are part of a compilation unit upload just fine. Any files that are not referenced in a Makefile, however, are uploaded to the server in a corrupt form (all null characters). It affects any raw text/data files that are part of the project. It also affects .cpp and .hpp files that are not part of a makefile/compilation unit. Even if the file has the 'Add to Parse' property enabled, only a corrupt version of the file is uploaded to the server. The workaround suggested by 'Mrugendra@netbeans.org' still works for source files in 8.0.2: right click on the file and select "Upload to me@myserver.com". However, this workaround IS NOT AVAILABLE for raw text files, property files, or other kinds of data. The only possibility I know if is to manually transfer correct versions of the corrupted files every time they change.
What if you use "SFTP" instead of "Auto copy"? does the problem exist in this case?
I run into the same issue with corrupted files on transfer. Unfortunately, it is not possible to test SFTP option on my setup. Are there any other ways to debug the issue?
(In reply to mathway from comment #7) > I run into the same issue with corrupted files on transfer. Unfortunately, > it is not possible to test SFTP option on my setup. Are there any other > ways to debug the issue? Why is it not possible to test SFTP? I think there is a misunderstanding here. I can not imagine circumstances that would cause SFTP mode not work while Auto Copy works. By working via SFTP I mean, that you go to the your remote hosts list, select "Properties" from context menu and in "Access Project Files Via" select "SFTP" instead of "Auto Copy".
(In reply to Vladimir Kvashin from comment #8) > (In reply to mathway from comment #7) > > I run into the same issue with corrupted files on transfer. Unfortunately, > > it is not possible to test SFTP option on my setup. Are there any other > > ways to debug the issue? > Why is it not possible to test SFTP? I think there is a misunderstanding > here. My bad, I misunderstood your suggestion. Yes, "SFTP" transfer works properly. So the issue is with "Auto Copy" method.