You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: Developers are checking in launch configuration into a code repository so that the entire team uses the same settings.
Now as a developer i want to customize an existing configuration to adopt some settings (xmx, plug-ins). Currently i have to derive from the existing configuration and choose a new unique name. This is annoying in the case that the configuration is referenced in a shared launch group. I would now also need to change the launch group.
Would be nice to have a feature that allows me to overwrite settings of an existing configuration. It should be validated that there can only be a single configuration that overwrites an existing configuration.
The text was updated successfully, but these errors were encountered:
I'm thinking about implementing this as a kind of orthogonal concept to inheritance. Adding the possibility to "patch" configurations without extending would do what you want.
The real benefit here is that existing things (like launch groups) don't need to be changed to use the extended configuration, but can continue to use the original one.
Scenario: Developers are checking in launch configuration into a code repository so that the entire team uses the same settings.
Now as a developer i want to customize an existing configuration to adopt some settings (xmx, plug-ins). Currently i have to derive from the existing configuration and choose a new unique name. This is annoying in the case that the configuration is referenced in a shared launch group. I would now also need to change the launch group.
Would be nice to have a feature that allows me to overwrite settings of an existing configuration. It should be validated that there can only be a single configuration that overwrites an existing configuration.
The text was updated successfully, but these errors were encountered: