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: | Disable upload on save when updating from versioning | ||
|---|---|---|---|
| Product: | php | Reporter: | crazyfacka |
| Component: | FTP Support | Assignee: | Tomas Mysik <tmysik> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | ovrabec |
| Priority: | P3 | ||
| Version: | 7.3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
crazyfacka
2013-03-09 18:13:54 UTC
(In reply to comment #0) > When performing an update to the whole project, if upload on save is selected > for the PHP project, all updated files will be uploaded to the server, > discarding changes made in the meantime by fellow workers. Well, mixing SCM and FTP is not a good idea, ever. @ovrabec: Ondro, is it possible to recognize which event comes from versiong support? Thanks. (In reply to comment #1) > @ovrabec: Ondro, is it possible to recognize which event comes from versiong > support? Versioning - in some cases such as versioning update in NetBeans, definitely not externally using other tools - can say what files really changed. But AFAIK PHP catches events coming from FileSystem and not Versioning (VCS does not fire any such events). PHP could probably catch "beforeChange" and "afterChange/Delete/Create" events the same way versioning does. The "beforeChange" event is fired from FS when a file is being saved by NB (using save action, refactoring etc.) and the "after" events are fired either when the save finishes or an external change (such as VCS update) is detected. So PHP may call copy-on-save only if a "beforeChange" event was delivered before. However i am not sure how reliable it would be, plus you would probably need to depend on other masterfs SPIs (see masterfs...ProvidedExtensions). Thanks a lot Ondro, I will look at it. |