Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] User-specific Launch Configuration Attributes
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.

On Mon, Dec 1, 2014 at 2:41 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
Hey CDT and PTP gangs,

As I plow through making a remote launch configuration type for CDT that uses o.e.remote.IRemoteConnections as the underlying launch target, I’m faced with a dilemma I’m sure many of you have had to deal with.

Attributes you specify in a ILaunchConfiguration are meant to be shared with other users. By default, this doesn’t happen and the launch config is stored locally, but sharing a launch config into your workspace and checking it into source control is only a few clicks away. I think we tend to forget that.

At any rate, at least for embedded, the identification of the remote you want to launch on generally can’t be shared with other users. It usually has a user specified name as well as their login credentials.

The problem is, there really isn’t a method to store user specific launch configuration settings such as this, at least none that I’m aware of. How have others solved this problem? Or did you just save the remote information in the launch config anyway and dealt with it when another user tried to launch that config? Is there interest in a common solution and if so, where would be the best place to put it for Luna SR-2?

Thanks,
Doug.

_______________________________________________
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

Back to the top