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 pretty much says it all. When a Build All is performed, errors are reported because the sources don't exist locally anymore.
Probably cannot be easily fixed, but maybe...
*** Bug 9630 has been marked as a duplicate of this bug. ***
Should be resolved now, since issue #11036 was resolved.
[NB32-38, RC4] I'm sorry but it isn't fixed. Reproduction: ============= Create a package create a few class files in this package and above package add & commit them all into repository. some of them remove [Localy removed] now on the root of FS "Build All" To the output window is written lots of messages like this: Packa/dfs.java [0:0] No file named Packa/dfs.java exists on disk in CVS /home.net/dm103276/.A/Build.Test/CVS/testonly/w6. Therefore it may not be compiled with an external compiler. You may need to check it out from version control or save some changes to it. Errors compiling dfs [Locally Removed; -1.1]. And in the Status line is possible read: Errors compiling. And NO [up-to-date] files are compiled.
Jesse, is it possible to patch/fix the ExternalCompilerGroup so it filters out ExternalCompilers that aren't present locally ?
It would be possible, but I think a bad idea--you want an error message in general, because someone is trying to do something which should not be done, i.e. compile a file which does not exist. I believe it is a bug in the VCS that it provides file objects for things you have removed locally--in your intended state of the project, before committing, the file is gone, so the IDE should treat it as gone. In contrast, files which are in the repository but not checked out are really supposed to be there, and you just need to update to get things fixed.
I think this issue is probably fixed with the introduction of VirtualDataObjects (anything that is not present locally but should be in the vcs filesystem) This dataobject doesn't provide compile capabilities. At least when I was testing the functionality, it behaved correctly. Otherwise it's a bug I think.
Yes Milos, you're right. The implementation of virtual data objects is done in vcscore, therefore it should work in vcscvs module also. (In NetBeans 3.3).
Okay, it seems that virtual nodes are not compiled any longer. I tried it on these statuses: [Needs Update], [Needs Checkout], [Locally Remo- ved] and [Missing]. Verified in Beta 6 build #200111271845 of NetBeans 3.3.
Resolved for 3.4.x or earlier, no new info since then -> closing.