| Summary: | Get rid of the internal usage of APIs using an adapter | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | amehrega |
| Component: | TPTP | Assignee: | amehrega |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | sluiman |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
amehrega
The eclipse folks assumed that we were only speaking of workbench parts that we had implemented ourselves. Marking this as invalid. Re-opening this as an enhancement and setting the version to 4.2. We need to use the new package fragment that is offered by Eclipse. See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=109052 Find out if we should resort to internal APIs if this package is not available in the user's plugin directory. There is a defect opened regarding this issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=126580 *** This bug has been marked as a duplicate of 126580 *** ACTION: Please verify/close this defect. Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct. |