This week I thought to myself, "lets fix a really old bug that has been marked LATER". So I went off looking for a bug or enhancement to try and find a good one. The best I could come with was importing and exporting launch configurations, bug 12898 (to and from the local file system). Rest assured there were a lot of cool bugs, but I also had to find one that would not take a long time to fix...
A good part of the idea behind this one was that not everyone uses CVS (or a variant) to share code (making shared configs almost useless). Most people also do not know where launch configuration files are stored in their workspace. With that in mind you can now fire up the export wizard, choose launch configurations, select the ones you want and the location to save them and PRESTO (not the pasta sauce) you get an instant copy of the selected configurations in that new location.
The export wizard
The configuration export wizard
Now lets say you have you have a bunch of launch configurations in a folder that you would like in your workspace, you can use the import wizard to make this happen. The import wizard uses the standard 'import resources' widgetry, so there should be nothing new in this wizard page (provided you have imported something from your file system before).
The import wizard
The configuration import wizard