Home » Modeling » QVT-OML » Posible enhacements in the QVT code
Posible enhacements in the QVT code [message #1211634] |
Tue, 26 November 2013 14:45 |
Victor Roldan Betancort Messages: 524 Registered: July 2009 |
Senior Member |
|
|
Hi all,
we use QVTo for our stack of model transformations in our products. We historically had to modify some plugins to mainly avoid undesirable dependencies in our products and other issues. I'd like to share this improvements here, looking for a chance to contribute them and finally getting rid of them. Im using the Kepler release, btw.
- org.eclipse.m2m.qvt.oml.emf.util.ui. States depends on Java 1.5, but uses Java 1.6 API. This shows compilations errors when using Java 1.5 compliance in the workspace. Probably the original developer had its workspace improperly setup. Affected classes:
* Line 55, ResourceDesintationChooser.
* Line 64, ResourceSourceChooser.
* Line 38, ResourceSourceDestChooser.
Solution -> replace by String.length() == 0
- org.eclipse.m2m.qvt.oml.emf.util.ui. Dependency on org.eclipse.emf.codegen.ecore.ui. It does not actually depend in any specific API of that bundle, but rather depends in reexports. I'd suggest to change to the actual dependencies, however, that would imply breaking clients (unfortunately, it's reexported). If you're still interested, it should be substituted by:
* org.eclipse.emf.ecore.edit;bundle-version="[2.5.0,3.0.0)",
* org.eclipse.emf.edit.ui;bundle-version="[2.5.0,3.0.0)",
* org.eclipse.ui.ide;bundle-version="[3.5.0,4.0.0)"
- org.eclipse.m2m.qvt.oml.editor.ui. We do not include JDT in our products, but this plugins depends on the JDT API, and makes it mandatory to have the whole JDT feature in our RCP, basically just for icons and a view ID. I understand its not desirable duplicate icons, neither hardcode view IDs, but I'd like to put this out, maybe there are better options. For instance, refactoring those dependencies in a new bundle (org.eclipse.m2m.qvt.oml.editor.jdt.ui).
So thats all. If any of the above sounds reasonable, I could provide some patches.
Best Regards!
Víctor Roldán [Open Canarias]
|
|
| | | |
Re: Posible enhacements in the QVT code [message #1214055 is a reply to message #1211634] |
Wed, 27 November 2013 14:18 |
Ed Willink Messages: 7669 Registered: July 2009 |
Senior Member |
|
|
Hi
On 26/11/2013 14:45, Victor Roldan Betancort wrote:
> - org.eclipse.m2m.qvt.oml.emf.util.ui. States depends on Java 1.5, but
> uses Java 1.6 API. This shows compilations errors when using Java 1.5
> compliance in the workspace. Probably the original developer had its
> workspace improperly setup. Affected classes:
> * Line 55, ResourceDesintationChooser.
> * Line 64, ResourceSourceChooser.
> * Line 38, ResourceSourceDestChooser.
> Solution -> replace by String.length() == 0
This was fixed by commit 355aa060932b4bfdca1dbdfe896be02dc177d274 on
2013-07-18 15:59:15
> - org.eclipse.m2m.qvt.oml.emf.util.ui. Dependency on
> org.eclipse.emf.codegen.ecore.ui. It does not actually depend in any
> specific API of that bundle, but rather depends in reexports. I'd
> suggest to change to the actual dependencies, however, that would
> imply breaking clients (unfortunately, it's reexported). If you're
> still interested, it should be substituted by:
> * org.eclipse.emf.ecore.edit;bundle-version="[2.5.0,3.0.0)",
> * org.eclipse.emf.edit.ui;bundle-version="[2.5.0,3.0.0)",
> * org.eclipse.ui.ide;bundle-version="[3.5.0,4.0.0)"
This is trivial; no need for a patch; just a Bugzilla for tracking.
>
> - org.eclipse.m2m.qvt.oml.editor.ui. We do not include JDT in our
> products, but this plugins depends on the JDT API, and makes it
> mandatory to have the whole JDT feature in our RCP, basically just for
> icons and a view ID. I understand its not desirable duplicate icons,
> neither hardcode view IDs, but I'd like to put this out, maybe there
> are better options. For instance, refactoring those dependencies in a
> new bundle (org.eclipse.m2m.qvt.oml.editor.jdt.ui).
QVTo already has image registries. It is probably easy to reuse
something already within QVTo to replace JavaUI.getSharedImages(); e.g.
CompletionProposalUtil.getImage(). If you got a few spare moments you
can see how many other equivalent registries have appeared through
diverse development.
The four *.gif files can then be copied to the local icons folder. No
need for an extra plugin.
Regards
Ed Willink
|
|
| | | | | | | | |
Goto Forum:
Current Time: Sun Sep 15 16:31:37 GMT 2024
Powered by FUDForum. Page generated in 0.06145 seconds
|