Bugzilla – Full Text Bug Listing
| Summary: | Juno contribution: org.eclipse.xtext.gmf.glue_0.9.0 | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Dennis Huebner <dennis.huebner> |
| Component: | Core | Assignee: | Patrick Tessier <Patrick.Tessier> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | rschnekenburger, sebastian.zarnekow, sebastien.gerard, sven.efftinge, vincent.lorenzo |
| Version: | unspecified | ||
| Target Milestone: | M7 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 368542 | ||
|
Description
Dennis Huebner
Any thoughts about ... ? Hi Dennis, Sorry for the delay. This bug seems quite important for the incoming release Juno. What I propose is the following solution: - we create a new plugin in the papyrus namespace from our side to extend the o.e.x.gmf.glue as we need for Papyrus tool. This new plugin will depend from yours. - we would propose you a patch in case of requireed fixes for some attributes or method - private to protected visiblity or exported packages modification. Our prerequisite is that the oex.gmf.glue plugin should be accessible for installation using p2, in order to be able to install it during Papyrus build and/or installation. It this plugin currently part of the simultaneous release? Does this sound good to you? Cheers, Rémi The xtext.gmf.glue plugin is only part of an example that we ship. You shold not depend on it but materialize it in your workspace, rename the plugin and packages accordingly and ship your own version. Please note that Xtext 2.3 is part of the train as well and since the plugins contribute to extension points some of them are marked as singleton. It is not possible to install different versions in parallel. Just m2c. Remi,
> It this plugin currently part of the simultaneous release?
Yes and no. It's a part of o.e.x.xtext.ui.examples bundle. But in the "zipped state of matter" :) so can't be installed with p2
I think the best solution is to clone and rename the project examples/org.eclipse.xtext.xtext.ui.examples/contents/org.eclipse.xtext.gmf.glue like Sebastian suggests.
Best regards,
Dennis.
(In reply to comment #4) > I think the best solution is to clone and rename the project > examples/org.eclipse.xtext.xtext.ui.examples/contents/org.eclipse.xtext.gmf.glue > like Sebastian suggests. Yes, that's definitely the way to go and please use the papyrus namespace. Thanks for your fast replies. We will switch our clone to the papyrus namespace. I close this bug as soon as the plugin has moved. Rémi Bug is closed, as contribution org.eclipse.papyrus.xwt has been approved in CQ 6333 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6333 (In reply to comment #7) > Bug is closed, as contribution org.eclipse.papyrus.xwt has been approved in CQ > 6333 > https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6333 org.eclipse.papyrus.infra.gmfdiag.xtext should be read here instead of xwt... |