| Not if they both used the same connection name. Maybe you could use the target name (or something similar) as the connection name and have this pre-filled so the user doesn’t set it. Greg
I think that’s how it’s commonly done. We used to do it that way in Momentics too.
My main problem with that approach is that the second user then checks in his version of the connection and the first users does a pull and loses his setting.
As I build the new remote launch for CDT, I’d like to fix that.
Doug.
Cool. What happens when the user checks in the launch configuration to source control and a different user checks it out and the connection ID isn’t defined?
It would try to find it, fail, and just be ignored. The user would then need to select one of their existing connections or create a new one.
My thinking is to do the same, but to store the ID/name of the connection and the launch config name and container path in preference store.
Doug.
We just store a tuple comprising the remote services ID and connection name. This uniquely identifies the connection. The remote framework take care of persisting the connection information and using secure storage for passwords.
Greg
Yes, the IRemoteConnection stores the necessary information for us to launch a process on the target. What’s missing is the mapping from Launch Configuration to target. This mapping needs to be independent of the launch bar settings since the
launch bar is optional. So I need to find a way to do it with out it. Org.eclipse.remote doesn’t have the concept of active target so relying on the target management system to provide one probably wasn't the right approach anyway. It seems like an artificial
creation that could be done in a more user friendly way.
The good thing is that ILaunchConfiguration is IAdaptable. So I could create an adapter that returns the IRemoteConnection. The Remote framework would need to provide an API to bind launch configs to connections and restore them on start up, much
like we’ve already been doing with ILaunchTarget. This could be set up in the launch config dialog for the remote launch I’m creating. (not everything has to go into the working copy). Shouldn’t be too hard.
But I am still wondering how others manage remote launches like this. We can talk about this at the meeting tomorrow.
Doug.
Why launch configuration needs to store connection information? Isn't the point of toolbar it to actually separate it and replace with concept of active target/connection?
Then user name/password should be stored in secure storage which eclipse deals with natively.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
