Option level configuration
I have some questions about the different option levels that are available
(i.e. Project, User, Default). I like the way when you change a default
option it moves it into the user level. Is there a way to overwrite the
default options that are available? We want to add several default VMs and
Projects that will be available to several developers. I can put all of
those settings into the User level for each developer, but the problem with
that is when they change the settings it actually changes it without
creating a copy or moving down a level.
Is there perhaps some documentation that explains the layout of the files
used by nbean? Our main goal here is to setup a consistent working
environment that does not require manual tweaking by the users. Does anyone
have an suggestions for possible nbean configurations to help us reach our
goal?
Lance
# 1
Johnson, Lance wrote:
> I have some questions about the different option levels that are available
> (i.e. Project, User, Default). I like the way when you change a default
> option it moves it into the user level. Is there a way to overwrite the
> default options that are available? We want to add several default VMs and
> Projects that will be available to several developers. I can put all of
> those settings into the User level for each developer, but the problem with
> that is when they change the settings it actually changes it without
> creating a copy or moving down a level.
Undocumented stuff you can try: in your copy (i.e. user dir), make some
customizations however you like. Now on disk, go to
$userdir/system/Projects/$projectname/system/ and you will have all
settings related to that project - pick some of them. ZIP them up. Also
ZIP up stuff in $userdir/system/ (but not in the subdir above) - this is
"user" settings. You can then unzip these files into another user dir,
or another project dir, or even into $nbinstall/system/ to set defaults
for all users of a given NB installation (each userdir can override them).
It is not too hard to figure out which file name corresponds to which
setting. When you change a setting, it is written to disk, so look at
timestamps. If you change it on disk, it is reloaded (after say fifteen
seconds, to check for changes). If you delete a setting customization
from disk, it is reverted to the default (again after a brief delay
perhaps).
Note that some kinds of settings are inherently hard to share. For
example, filesystem mounts normally include a disk path which is not
likely to apply on a different machine (unless everyone uses NFS or
Windows shared drives, e.g.). NetBeans does not currently provide a good
solution to this problem; 4.0 is expected to, when the whole system of
projects is overhauled (see projects.netbeans.org for the gory details).
-Jesse
--
Jesse Glick <mailto:jesse.glick@sun.com> x22801
NetBeans, Open APIs <http://www.netbeans.org/>
