> > -) Backup of old versions > > -) Rollback to older versions > > -) Command-line and GUI interface (for those X-impaired people) > > -) Proxy support (maybe) > >Figuring out which bundles are updated could be accomplished by looking in > >a central file or searching a remote filesystem, although I favor the > >former. > Here's one: How about renaming or deleting legacy JDEE variables not used in > the new JDEE package? I just went through this very annoying process while > customizing jde-key-bindings and trying to save my changes for the current > session. Emacs kept prompting me of "Invalid functions" (for > jde-complete-at-point-menu, for example) still mapped to keys. > I think that Klaus Berndl ([EMAIL PROTECTED]), author of ECB has a hack to > do this. > Another feature of the Installer could the creation of an install log file. > If it's going to mess around in the .emacs, then it should log all steps and > make a backup of the original .emacs before it changes it. Look, I am not en emacs expert and not JDEE expert. So I created simple installation script which will help me (and possibly other developers) to install/upgrade. It just simplifiers downloading, unpacking, compiling libraries nothing more. And I don't plan to extend it much more. I even don't know about all changes made in each release. So making corrections in config files (.emacs and prj.el) seems too complex for me. I am not sure if this is even possible regarding to complexity of .emacs files.
So if you have ideas, power and knowledge feel free to take this script and extend it with any feature you like. If you plan to create installer with GUI my script will not be even useful. Artur Hefczyc -- Artur Hefczyc [EMAIL PROTECTED] http://wttools.sourceforge.net/ http://geotools.sourceforge.net/
