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: | [67cat] Non-working SFTP deployment due to a script error | ||
|---|---|---|---|
| Product: | javame | Reporter: | hotxrock <hotxrock> |
| Component: | -- Other -- | Assignee: | issues@mobility <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | sustaining |
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | TASK | Exception Reporter: | |
| Attachments: |
Fixes incorrect arguments in the script
Patch fixing the issue |
||
Created attachment 75777 [details]
Fixes incorrect arguments in the script
The issue hasn't passed the nomination process for 65patch2 by cut-off date. It has been moved to 65patch3. The status whiteboard "65fixes4-candidate" has been removed. At this time our proactive patches for the NetBeans 6.5.x IDE have concluded. If you own a Sun service plan contract for NetBeans, you may wish to contact Sun Service http://www.sun.com/contact/support.jsp to request a fix via the product defect escalation process. For more information on purchasing a Sun service plan contract for NetBeans, refer to the service plan item "Sun Software Service Plans (S3P) for Developers" in the Sun Service table found on our NetBeans Support Resources page http://www.netbeans.org/kb/support.html I've downloaded NetBeans 6.7 beta and I see that this bug is still there, so I upload a patch fixing this issue again. It's not good that SFTP deployment doesn't work at all because of invalid data in a single line. Created attachment 81471 [details]
Patch fixing the issue
Fixed in CS 44e7be65bd20 |
Bug: SFTP deployment doesn't upload anything to the server, NetBeans connects properly, but files are not transferred. Cause: fileset tag in the deploy-scp-impl.xml script contains invalid parameter dir = "${basedir}" instead of dir = "${deployment.dir}" I've fixed this in the patch, maybe we can include this issue into 6.5 patch 2. Sorry that I've come up with this so late, but I've just rememebered about this bug.