Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364973 - Better tooling for Jubula Extensions
Summary: Better tooling for Jubula Extensions
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: Tools (show other bugs)
Version: 1.1.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-28 11:21 EST by Zeb Ford-Reitz CLA
Modified: 2013-12-17 07:43 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zeb Ford-Reitz CLA 2011-11-28 11:21:13 EST
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.
Comment 1 Alexandra Schladebeck CLA 2013-12-13 09:08:44 EST
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.
Comment 2 Oliver Goetz CLA 2013-12-17 07:43:36 EST
Closed due to comment 1