Community
Participate
Working Groups
Build Identifier: 20110615-0604 Adding XBase support to a freshly generated xtext project is complicated because plugin.xml does not exist yet, and there is no way how to generate it since workflow will fail due to missing xbase dependencies. Reproducible: Always Steps to Reproduce: 1. create a new project using xtext wizard (New Project -> XText) (note: plugin.xml file is not created at this stage, perhaps this is the issue) 2. create your new grammar using Xbase, that is: grammar org.xtext.example.Lang3 with org.eclipse.xtext.xbase.Xbase (in my case I copied the grammar from another project) 3. editor already indicates errors. If workflow is run, it blows with: Caused by: java.io.IOException: The path '/org.eclipse.xtext.xbase/model/Xbase.genmodel' is unmapped It is easy get around. Just before user implements his grammar he has to run workflow (using pregenerated xtext gramma stub). This creates plugin.xml and in the next iteration, finanlly he can start implementing the grammar and he has existing plugin.xml to add the XBase packages to. To fix this issue properly, create project wizard should offer to include XBase support and create plugin.xml early on. This is a low impact bug.
Please note that the only required change is a require bundle in the manifest.mf (Open Manifest.MF -> Dependencies -> Add -> *.xbase -> Enter) Closed as won't fix since I don't think that's complicated. Please reopen if I missed your point.
I see. My bad, you are right. I considered plugin.xml to be something like pom.xml from the Maven world. Double clicking on Manifest.MF actually opens the same dialog as clicking on plugin.xml. I did not know that. Some king of documentation about Eclipse/OSGI related stuff in Xtext would be highly appreciated!
Closing all bugs that were set to RESOLVED before Neon.0
