Menu
▾
▴
#78 Version upgrades corrupt the existing configuration
When a new version of JCommander is started the
existing configuration is reset. All tabs info is lost
too. This is a serious usability issue since it
basically is a data loss.
The following things should be done to fix the current
faulty behavior:
- the ~/jcommander.conf file, if exists, should not be
reset on a fresh startup - the ~/jcommander.jcmdbmk file, if exists, should
remain unchanged - the workspace should be moved to the user's home dir (~)
In fact if issue 3 would be solved that might
automatically fix issues 1 and 2.
Logged In: YES
user_id=940779
As configuration format might change between versions
specifying the current jcmd version in the config files is a
must so that in the future config format conversions can be
done.