Custom Query (4 matches)
Results (1 - 3 of 4)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1 | fixed | Update core functionality to current environment | hkaulbersch | phdmakk |
Description |
The implementation as a whole is based on outdated technologies and does not work with current versions of Eclipse (Kepler) and Xtext (2.x) among other components. Update the core functionality by migrating to current version of Eclipse and Xtext. Core functionality encompasses parsing and editing support, i.e. the most basic building blocks provided by Xtext. This can be achieved "in-place" - by working with the existing resources directly, or "in parallel" - by starting from a clean state in a new parallel location and migrating relevant resources as necessary, while the original resources are kept for reference. I would recommend the latter, but this is not to say that the former would not be possible. |
|||
#9 | fixed | Review and resolve open tickets that have been implemented | hkaulbersch | phdmakk |
Description |
Partially implemented features may be closed as well with a note on the state of the implementation and open issues. If there is a need for further work on these tasks, they will be reopened in the future. Relevant commits may be indicated by appropriate trac-links. |
|||
#6 | fixed | Investigate and realise deployment strategies | hkaulbersch | phdmakk |
Description |
The easiest approach is to export the tooling as a plugin. Investigate how this can be best achieved and possibly automated (e.g. for nightly builds). Alternatively, a lightweight and environment independent solution would be to deploy the tooling as an RCP application. Investigate how this can be best achieved and what possible drawback it may entail. If the effort is too high, this option could be postponed or discarded. |