| Summary: | cannot compile Xtext 2 sources | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Lorenzo Bettini <lorenzo.bettini> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | moritz.eysholdt, sebastian.zarnekow |
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Lorenzo Bettini
make sure to use the source from git rather than CVS. CVS is deprecated for Xtext, MWE and Xpand. http://git.eclipse.org/c/tmf/org.eclipse.xtext.git/ http://git.eclipse.org/c/emf/org.eclipse.mwe.git/ http://git.eclipse.org/c/m2t/org.eclipse.xpand.git/ some updates: I imported in the workspace all the projects of the plugins directory of http://git.eclipse.org/c/emf/org.eclipse.mwe.git/ http://git.eclipse.org/c/m2t/org.eclipse.xpand.git/ and it looks most of xtext plugins can be built... I still have problems with org.eclipse.xtext.ecore (The type org.eclipse.emf.mwe2.runtime.workflow.IWorkflowComponent cannot be resolved. It is indirectly referenced from required .class files EcoreSupport.java /org.eclipse.xtext.ecore/src/org/eclipse/xtext/ecore line 38 Java Problem), org.eclipse.xtext.xtend2 (problems in Xtend2.xtext) and some on Xbase.xtext and Xtype.xtext but I guess these are due to the fact that these grammars rely on xtext2 (which is what is being built in the current workspace), thus it should not be a problem, should it? > I still have problems with org.eclipse.xtext.ecore (The type > org.eclipse.emf.mwe2.runtime.workflow.IWorkflowComponent cannot be resolved. It > is indirectly referenced from required .class files EcoreSupport.java > /org.eclipse.xtext.ecore/src/org/eclipse/xtext/ecore line 38 Java > Problem) IWorkflowComponent comes from bundle org.eclipse.emf.mwe2.runtime. Do you have that in your workspace? it compiles fine for me... > org.eclipse.xtext.xtend2 (problems in Xtend2.xtext) and some on > Xbase.xtext and Xtype.xtext but I guess these are due to the fact that these > grammars rely on xtext2 (which is what is being built in the current > workspace), thus it should not be a problem, should it? yes, the *.xtext grammars need Xtext2 to be displayed without error markers. That's not a problem since all workflows etc. will run anyway. If you want to get rid of theses errors, you'll need to upgrade Xtext in your host workbench to version 2.0. You can use the update sites or get an Eclipse Distro with M6 pre-installed from here: http://download.itemis.com/distros/ Please reopen if there is still an issue with the workspace setup Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |