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.
[200507061800] 1.Check out some module from netbeans cvs (e.g. a11y module - nothing else, just this module) 2.Start IDE with clear userdir 3.Try to open a11y module in netbeans It is not possible to open this project due to dependencies (all modules that a11y depends on must be checked out to be successful).
Yes, you have to check out the dependencies.
The user needs some feedback. There should be some warning that other modules must be checked out to be able open this project. Doe's it make sense?
Of course, but it is a special case of the more general problem that the NBM project type does a poor job of collecting and reporting configuration errors. Ideally it should be possible to open the project and later fix the platform etc., but we are not there yet - very unlikely to have time to do that before feature freeze, maybe during 4.2 bugfixing stage. I don't think there is any real debate about what the behavior *should* be, but we probably don't have enough time to make the error handling be as robust as for e.g. j2seproject's. A somewhat related issue with the project system generally is that the Open Project dialog does not display error messages when you click on a potential project folder (i.e. a localized annotation from an IOException thrown by ProjectManager.findProject). That would be a relatively simple thing to do that might help somewhat (in other cases too, not just for NBM projects).
Verified.