Unable to export/import Pydev run/debug launch configs

6 views
Skip to first unread message

Kenneth Loafman

unread,
Aug 18, 2016, 2:02:18 PM8/18/16
to licl...@googlegroups.com
Hi,

The update site does not work for Mac OS X, so I have to install a new copy, reinstall all the addons, import preferences, altogether a couple of hours of downtime for each upgrade.

So today I tried exporting and importing launch configs as well, coming from 3.01, going into 3.10.  The external launch configs make it in, but the run/debug launch configs don't make it .  I use a lot of these and having to manually rebuild is a real PITA.

Any ideas on how to fix this?

...Thanks,
...Ken

Fabio Zadrozny

unread,
Aug 18, 2016, 2:23:32 PM8/18/16
to Kenneth Loafman, licl...@googlegroups.com
​Hi Kenneth,
 

The update site does not work for Mac OS X, so I have to install a new copy, reinstall all the addons, import preferences, altogether a couple of hours of downtime for each upgrade.

​Humm, really weird that the updates don't work... can you explain what exactly doesn't work? Which error do you have?
 

So today I tried exporting and importing launch configs as well, coming from 3.01, going into 3.10.  The external launch configs make it in, but the run/debug launch configs don't make it .  I use a lot of these and having to manually rebuild is a real PITA.

​Actually, if you go to the menu > Run > Run Configurations > select launch > common, you can save the launch as a shared file in a project (so, you could even commit those and anyone with the same project could have the same launches -- if they're important to you, you can even have a project just for those launches and save them in a git repo). 

But still, this shouldn't really be needed... even if you install a new version of LiClipse and other add ons, if you point to the same workspace, everything should be ​restored to where it was (projects, launch configurations, preferences, etc) -- personally, this is what I do: just extract LiClipse to a new folder and when starting up point to the workspace I was already using and everything is kept as it was.

Best Regards,

Fabio
Reply all
Reply to author
Forward
0 new messages