Bugzilla – Full Text Bug Listing
| Summary: | Query2 Incompatiblity with Xtext2.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | saurav sarkar <saurav.sarkar1> | ||||
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | ashw.kumar, jan, sven.efftinge | ||||
| Version: | 2.0.0 | Flags: | jan:
indigo+
|
||||
| Target Milestone: | RC4 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Could you please provide the list of incompatibilities as plain text in a comment. The outline has been redesigned. The new outline API is described in the Help. The RC4 will contain a migration guide covering other changes. Regarding the restricted access. This is how we communicate what's API and what is not. It doesn't mean you can't use non API, it is just that the next release might not be a drop-in replacement if you use any of the provisional APIs. (In reply to comment #1) > Could you please provide the list of incompatibilities as plain text in a > comment. > The outline has been redesigned. The new outline API is described in the Help. > The RC4 will contain a migration guide covering other changes. > Regarding the restricted access. This is how we communicate what's API and what > is not. > It doesn't mean you can't use non API, it is just that the next release might > not be a drop-in replacement if you use any of the provisional APIs. Hi Sven, Please find the list below (a)The method allInResource is removed now from the Scopes class. (b) The ParseTree package is not made accessible to any other plug-in.We used to use AbstractNode,CompositeNode,ParseTreeUtil,NodeUtil classes from that package. (c) org.eclipse.xtext.util.TextLocation not available. (d) ILocationInFileProvider.getLocation(Eobject object) is not available. (e) org.eclipse.xtext.ui.editor.outline.transformer is not exposed.We used AbstractDeclarativeSemanticModelTransformer. (g) org.eclipse.xtext.ui.editor.syntaxcoloring.antlr is not exposed.Generated UI module used AntlrTokenScanner. Furthermore i will check the outline APIs in the help. cheers, Saurav I've updated the migration guide. All your points should be covered, except from (a) which had already been deprecated. Please use a SimpleLocalScopeProvider instead. Hi Jan, From where can we access the migration guide ? Regards, Ashwani Kr Sharma EMF Query2 Committer It's in the repository : http://git.eclipse.org/c/tmf/org.eclipse.xtext.git/plain/plugins/org.eclipse.xtext.doc/contents/213-migrating-from-1.0.html Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |
Created attachment 197294 [details] Contains the screenshot for the incompatiblity list Hi All, Query2's String syntax feature depends on XText. With the advent of XText2.0 we few problems. I have attached the screenshot for the incompatiblities which we have found. I have also done an intital analysis for them.Like IUnitOfWork's package has been changed to org.eclipse.xtext.util.concurrent . So this kind of migration we can do from our side. But i also see lots of class access has been restricted and some Outline API restructuring.We would need help on these resolving those kind of issues. Please provide your comments/suggestions on this.Let me know if the attachement is not clear. cheers, Saurav