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: | Sharable property storage for automatic projects | ||
|---|---|---|---|
| Product: | projects | Reporter: | Jesse Glick <jglick> |
| Component: | Autoproject | Assignee: | issues@projects <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | ||
| Priority: | P1 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 153235 | ||
It is desirable for a client of Cache to be able to mark a certain property as "sharable", i.e. the result of an explicit user configuration choice which is portable, rather than a temporary setting, or cached information from e.g. build sniffing. Such properties should likely be stored in a file ${basedir}/netbeans.properties. Existence of this file would also automatically mark the containing dir as an autoproject. Keys in the file would be implicitly prepended with "${basedir}/" so that they are relative, and would need to use '/' as a path separator. This means a change in the current interface to store a key - the key would need to consist of a (File,String) pair. Perhaps the call should be made on an AutomaticProject instance so that the basedir is clear. Creation of such a file should be done only upon user request. This could perhaps be a context menu item on the project's root node; or a checkbox in the New Project wizard. The former would give you the ability to remove netbeans.properties while moving its contents to your private settings area. If netbeans.properties is created after a project already has had some keys stored, the sharable ones should be moved into the new file. This means that when netbeans.properties does not exist, any keys stored that are marked sharable should be notated as sharable even in the private storage.