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.
When you build the project remotely in Smart Secure Copy mode, all files are copied over and the project is being built. Good. But the built artifact (binary, library, package) stays in the cache on the remote host and there is no good way to retrieve it. You cannot sync the entire project, only selected source folders. So it is rather pointless to built the project remotely if you are interested in these artifacts. 1) As a minimum I would expect I could sync the entire project so the dist folder on the local host would get updated with the remotely built artifact. 2) And better, when building remotely in this mode, the system should automatically sync (download) the dist folder from the remote host to the local host. This would work only for managed projects. Unmanaged projects would need the first option.
Perhaps it should automatically sync all files after the build so the project on the local host gets updated with all built artifacts. If you cannot get to the artifacts, building in this mode is kind of pointless.
What's the use of bits for another architecture on the local machine? For example, why would user need Solaris bits on Windows? Well, there probably might be some use... but, IMHO, not much enough to make it P2, DEFECT and 6.8
If you are on Windows/Mac/Linux and want to create a Solaris zip/tar/SVR4 package to give to somebody, you can built it but you can get it! Isn't that the entire purpose of remote that you do those kind of things?
I see your point. Anyhow it's too late to make it right now. And how is packaging implemented? If it is implemented via some tools invocation (tar, zip, etc) - then it just can be done on remote host. I guess for SVR4 that's the only correct way.
What is the point of a binary can be build and runs correctly on a certain platform if you cannot get to it and do something with it? People wants to build on a remote host for a reason, and I think the reason is more than just knowing it can be build. They must be interested in the build artifacts in some way. And if you can't get them, I think it is rather pointless to begin with.
I didn't mean the issue isn't valid. It is. I agree that user might be interested in artifacts. A good example is the packaging result (zip, tar, SVR4) - I think user would like to have it locally, even if this package is built on remote host.
I think Thomas made a good point, but to me it sounds more like an important (may be P1) enhancement. And I agree with Vladimir that it is too late in the cycle to introduce such a functionality. Moreover I do not think the download must be done automatically. A user may build many many times and may need to access the artefacts once a week or so. Once we have remote browser implemented it all will be much easier.