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 coping a directory, the CVS information is copied as well. Here is what I did: ProjectA/nbproject/subdir/subdir2 ProjectB/nbproject/ - ProjectA has the project information in CVS - I created a new netbeans project, ProjectB. - I copied "subdir" from projectA into the nbproject directory of ProjectB. Since ProjectB was not yet in version control, the nbproject directory was [local], but the new directory and files showed sticky tags from where they were copied from. This was a bit bewildering until I figured out what was going on and deleted the CVS directories.
This is unsolvable with the current APIs. The filesystem have no idea about copy operations, it gets just events for individual file creation and I/O operation. Filesystems would need a copy operation.
This is definitely a defect. It may require "enhancing" the APIs to fix, but if you copy directories with netbeans you end up hosing yourself. If someone is not a bit savvy with how CVS works (and does not know to remove the CVS directories), they will be a state where they have files that cannot be used in conjunction with CVS at all. The files will also display confusing information as their status and version. I forgot this detail yesterday when I copied a directory and was pretty frustrated with the distraction.
Do you really need copy operation ? Isn't some flag like isCopyAllowed sufficient ? Moreover there isn't supported copying of "folders" in filesystems API. This is now responsibility of DataFolder isn't it ? There actually exists method isCopyAllowed in DataFolder. If there was method isCopyAllowed in FileObject then this method could be used in DataFolder. But other FS implementation than VCS won't probably care about CVS folder. Moeroever we are going to get rid of VCSFS. In addition there might be valid claim to copy all files including CVS folder - probably neither from project nor files view but if we had some pure file explorer. I think that there is obvious that this case is absolutely the same like visibility of files. I don't think that there is right solution to change filesystem API because of this issue. Reassigned back to vcscore.
Hmm, so we would have to create our own DataFolder, that would refuse to copy itself. In general VCS should assure that the versioning metadata will not be copied (this also affects VSS (vssver.scc) and PVCS (vcs.cfg)).
I've concluded that implementing our own VCS DataFolder is the only way to go (with the current APIs). It's not nice at all, but it's impossible to solve this on FileSystem layer. Starting to work on this...
Implemening a special VCS DataFolder in VCS modules is quite ugly. I would have to copy the appropriate loader. And nobody would be able to provide another DataFolder on versioned files. Probably a better approach arose from the discussion with Yarda - take the VisibilityQuery into account by the individual projects providers. I.e. copy only files that the user actually see. That will skip CVS folders and other "garbage" that is possibly there. Therefore copy actions in Projects and Files view will act in accordance with VisibilityQuery and copy action in Favorites (where *all* files are visible) will copy everything (like now). Tomas, can you please implement that in Java project? (and possibly Files view...)
OK
Fixed in PackageView: Checking in src/org/netbeans/spi/java/project/support/ui/PackageViewChildren.java; /cvs/java/project/src/org/netbeans/spi/java/project/support/ui/PackageViewChildren.java,v <-- PackageViewChildren.java new revision: 1.54; previous revision: 1.53 done
Fixed for package view. For thysical view it requires bigger change, probably new paste type (API) to allow to paste folders from the physical view into the logical view. Changing to promo-F
Partialy works (in the logical view works fine).
Works in logical view.
Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next".
NetBeans.org Migration: changing resolution from LATER to WONTFIX