Add a new launch target wizard that manages creating and editing of
launch targets (similar to the new CDT toolchain wizard).
Allow editing of launch configuration names in the descriptor edit
dialog.
Change-Id: I1c690a5c5d8a8a6d4e4698b47cd35e6cc40944c5
added some tests for LaunchTarget
hide some API's for LaunchTarget
added some asserts to prevent misuse
Change-Id: I8b5b59ea8901133e79d03afe55e6c1fca2762bc1
Added a whole bunch of APIs to the managers to enable this without
exposing internals to the control. Documentation will be added before
release.
Change-Id: I7a643eca3d48643e7a1202d83c7b4818722c54f0
Replace IRemoteConnection with ILaunchTarget. Launch target
providers that want to use IRemoteConnection can adapt to it.
Also removes IHoverProvider since tools tips on the target selector
use the status message for the target.
Change-Id: I117745e61789ef780c742da9b73bded2b598915c
launchConfigAdded becomes pretty important. Requires providers
to be able to find descriptor and target from the incoming
configuration if they own it. Also added handing for a default
when the target is null.
removed ownsConfiguration in providers since the launchConfigAdd
does that by returning false.
Added enablement for config providers, but that will need work
and some default property testers for it to be useful.
For the correct way to add in a config provider, check out the
Arduino change for this API at:
https://git.eclipse.org/r/#/c/49029/
Change-Id: I46b194a933c846d7d3e4eea8a0213c4ec324816f
- fixed tests and added tests for previous API changes
- fixed unsafe call of provider methods without catching exceptions
- added description of priority attribute in the extension point API
- fixed default return values in DefaultLaunchConfigProvider, in case it
is extended
- removed unused import
- fixed per target provider to support persistance
- added test for per target provider
Change-Id: If08b18b939e86757108a800d1092a62621a8c7d0
Also adds a tighter check for ownsConfiguration based on class name
of the provider that created the config.
Change-Id: If197246af0906cb5af92819171ee97dc7cd30bee
WTP needs a new config for every target. That breaks our architecture
of one config per target type. But that's actually already broken
since we can't really get the proper target to the launch config.
Depending on active, we always hoped the target didn't change, but
it can. So one config per target is correct anyway.
Change-Id: I14ba8413b9494a13f3496eed5535debbc330a56c
services
- if you select target for given launch config and restart IDE
it is not persistent, because it queries remote services and
it has not been set. Moving setting of target in the correct place
Note: if launch config is not created yet it would not be create
and mapping would not be set but it would be persisted by launch bar
itself
- also added protection against null listener
Change-Id: I41f8651ba2251ca9f841450fc1f511643bfde681
- also mocked another target so it does not always test local one
Change-Id: Idf59342aac75bf5c92c5ca63870eade760065f70
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
- restored test module in pom
- fixed tests - xml tag was renamed
- fixed tests - stub functionality that rely on o.e.remote
- fixed NPE when accesssing osname from LaunchTargetTypeInfo
- added guards when calling into user defined classes
- added more comments in java docs
- restored original launch bar tests
- current provider won't get notified when lc is removed, need to fix
more
Change-Id: I15f1a30e9f965ad5c84bdc51238ef129dc314450
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
ILaunchTarget is removed and replaced with IRemoteConnection. You
still have to declare a launch target type to point at a connection
type. It uses os and arch to help decide what toolchains to use for
builds.
Change-Id: I8f21b4e5043ccd8af85be91c643f58ad301c3ac4
