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: | NetBeans should provide some simple wildcard filters relating to projects | ||
---|---|---|---|
Product: | php | Reporter: | phpguru |
Component: | Project | Assignee: | Tomas Mysik <tmysik> |
Status: | NEW --- | ||
Severity: | normal | CC: | ovrabec |
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | Macintosh | ||
OS: | Mac OS X | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
phpguru
2013-08-23 08:06:01 UTC
I assume you're talking about PHP FTP support? Well, from your post i got the impression you're accessing remote files with two different channels: either via FTP or via version control. That's simply wrong and almost a stupid idea. I can barely understand the scenario with getting sources via version control from one server and upload them on save to another via FTP but having just one remote location and downloading/uploading the files with either VCS or FTP is really something i cannot grasp. The correct way to get files to your local machine is always via version control only when the project is already versioned. But passing to php owners to decide what to do with this request. I use PHP NetBeans, but I assume the process of creating a new site [either from SVN via team checkout or via download from remote] is quite similar regardless of the server side language being used. Having said that I agree that VCS should always be the go-to for first checkout and creating a project. But, in the case I describe, my "remote server" is a development server on which I have been performing changes using vi on the server over SSH. Now then, all I am really saying here is that if NetBeans were to simply download .svn folders (or .git folders, or other invisible files crucial for VSC system operation) then all would be good in the world, because NetBeans would just read the .svn info as it would do if I tar gzip'd the whole thing and downloaded it and made it a new project from existing sources. It is easily conceivable that my dev server has a working copy and relates to the run configuration, and that I have a working copy on my local machine, and that both my dev server and my local machine are able to access the SVN repo, is it not? In short, if NetBeans downloaded invisibles from remote, it would be better than it is now. If it had filter patterns to include or not include when downloading remote files for inclusion in the project and it observed the invisible files on a remote server, it would be more flexible for use cases you can barely conceive of, and in theory be easier to set up a new project. What I am forced to do now, given the methods currently provided in NetBeans, is SSH to the dev server, commit everything there using CLI tools (often painful, particularly if the commit fails due to conflicts), then create a new project that is unaware of the remote site using Team Checkout feature, then pushing all of the exact same files back to the remote server. I hope this explains why I don't think it is a stupid idea. |