I always found the procedure of updating the felix config rather annoying. I wasn't really aware of what actually has been changed and especially having to restore those few fields I've changed for my purpose, e.g. the database configuration is a dull task that's error prone.
No I figured out the following solution wich works great for me. Maybe someone else finds it useful. - Create a git repository in your felix' config dir and put anything inside. - Create a project in your IDE rooted in the config dir. I myself work with IntelliJ but I believe that the following will work the same in Eclipse. - Rsync from your working tree to the felix config - Now the crucial point: open the config project in your IDE. Watch the changes, keep some lines of your config, etc. In IntelliJ this is done very easily, changes in files are nicely marked in the gutter and when you hover them you get presented the diff. That can be restored with a click. - Commit the new config. How do you deal with that situation? Did you have similar problems with updating your felix conf? Or is it just me that ran into this? What did you do to work around this? Please share your thoughts. Thanks, Christoph _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
