Bugzilla – Full Text Bug Listing
| Summary: | Better tooling for Jubula Extensions | ||
|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Zeb Ford-Reitz <zeb.ford-reitz> |
| Component: | Tools | Assignee: | Project Inbox <jubula.tools-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | Oliver Goetz <Oliver.Goetz> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | alexandra.schladebeck |
| Version: | 1.1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Doing some pre-Christmas cleaning - I'm sorry that this didn't get commented on sooner. It is, in itself, an interesting enhancement. However, as the inactivity shows, it's not something that has made it high on the priorities list since it was entered. I'm going to resolve this as wontfix. If anyone has new / other information or arguments, please reopen. |
The current method of writing extensions sometimes makes the process unnecessarily difficult. The primary complaint that I have is that the extensions are written in XML without the kind of support that one might expect when writing XML ("code" completion, browsing available IDs, and value validation are a few examples that come to mind). I think that implementing the Extension mechanism as a series of extension points would greatly simplify the Extension process, as Eclipse's Plug-in Manifest Editor offers support for at least the points that I mentioned above.