| Summary: | [Tooling] RWT-Launcher tests don't have a launch configuration | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Beyhan Veliev <beyhan.veliev> | ||||
| Component: | Demo | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Beyhan Veliev
Created attachment 199230 [details]
launch configuration
Provides a launch configuration for RWT-Launcher. The applicable SWT-fragmen have to be selected to run the tests
To my knowledge, the launch config for 'RAP Tooling' already includes the RWT launcher bundle. If this isn't the case I would rather enhance RAP Tooling launchh config than create yet another launch config. Another problem that I see with launch configs that aren't plaform neutral (SWT fragment) is that they 'pollute' the synchronize view. As it isn't overly complicated to create an 'Eclipse Launch Configuration', I would rather not provide another launch config. (In reply to comment #2) Yes, I agree with you. I thought RWT-Launcher and RAP-Launcher should not have any dependencies. May be in the future we can provide RWT-Tooling and RAP-Tooling. For now it isn't a topic and we can close this bug as invalid. Closing as INVALID as suggested in comment #3 |