-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix maven build configuration, include MWE2 workflow execution for xtext generation #90
base: master
Are you sure you want to change the base?
Fix maven build configuration, include MWE2 workflow execution for xtext generation #90
Conversation
Conflicts: org.bbaw.bts.app.product/pom.xml org.bbaw.bts.corpus.text.egy.egydsl/pom.xml pom.xml
As described at https://eclipse.org/Xtext/documentation/350_continuous_integration.html > First you need to use a platform:resource URI instead of a classpath URI to > point to your Xtext grammar file. This is because we don�t have the source > folder on the classpath of the exec plug-in. To do so open the mwe file and > change the declaration of the grammarURI to a platform URI similar to how > it is done in the example.
…travis_CI_xtext
…travis_CI_xtext
Execution of EMF MWE2 workflow for code generation from xtext grammar successfully could be invoked by maven configuration when attribute
|
There is a problem with the editor part because for some reason |
Multiple modifications turned out to be necessary in order to get maven build to work on a fresh clone. Most importantly, though, execution of mwe2 workflow xtend script for xtext generation of egyptian transliteration notation grammar could be integrated into the build process.
This is a major improvement because so far, generation of the grammar code had to be run in eclipse in order to be able to build the application. Now everybody can build BTS without even having eclipse.