|
|
Re: Couldn't find AUT for ILaunch: org.eclipse.debug.core.Launch@1e8ab1fe [message #1842200 is a reply to message #1831032] |
Fri, 11 June 2021 09:58  |
Eclipse User |
|
|
|
Markus Modzelewski wrote on Mon, 10 August 2020 09:12We found a workaround for this (don't ask how...) for this:
- Go to your rcptt\workspace\.metadata\.plugins\org.eclipse.debug.core\.launches folder of your RCPTT Installation
- Open your <Application>.launch file. (<Application> is the name of your Application in Application View)
- Remove the strange line regarding the launch ID (e.g. <stringAttribute key="org.eclipse.rcptt.launching.ATTR_AUT_LAUNCH_ID" value="ea879584-ab1b-479a-90cb-0dcf7c0c52d1"/>)
- Restart your RCPTT Application
- After restart, AUT can be started again
does this attribute get inside the launch config when performing a Restart of the AUT, like this
restart-aut
wait-until-eclipse-is-ready
this doesn't work when started from RCPTT IDE for quite some time.
Do you have workaround for it?
|
|
|
Powered by
FUDForum. Page generated in 0.24169 seconds