-
Notifications
You must be signed in to change notification settings - Fork 28
-
Notifications
You must be signed in to change notification settings - Fork 28
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
get rid of fornax-oaw-m2-plugin & migrate to new workflow #249
Comments
fornax repo is down right now. already reported it |
fornax repo has broken signature. have reported that. |
pr'ed #266 for the obsolte fornax maven repo and pulling newer version from maven central |
new workflow comes more "urgent" eclipse/xtext#1669 am not sure if there is a proper replacement for StatefulLexerFragment |
this also prevent from moving the bundle dependency from manifest to build.properties main problem for moving to new workflow is: the stateful lexer fragment has no replacement unfortunately |
maybe we can as an immediate solution port to new workflow and use fragment adapter |
also the manifest deps to compile time only stuff is bad |
with the removal of orbit this becomes worse and worse cause the xpand dependency |
this is done |
code still uses fornax-oaw-m2-plugin.
we should consider moving to new workflows everywhere and use maven-exec
plugin to generate dsls. (as xtext new project wizard creates projects)
The text was updated successfully, but these errors were encountered: