Skip to content
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

DSL compilation error #5

Open
karussell opened this issue Nov 22, 2016 · 4 comments
Open

DSL compilation error #5

karussell opened this issue Nov 22, 2016 · 4 comments

Comments

@karussell
Copy link

karussell commented Nov 22, 2016

I've tried mvn clean install and got the following error. Does this really mean I need mono installed for a Java project :) ?

[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] Mono is required to run DSL compiler. Mono not detected or specified.
[ERROR] DSL compilation error
  Unable to setup DSL-JSON processing environment. Specify dsljson.loglevel=DEBUG for more information.
@cowtowncoder
Copy link
Owner

Sigh. Yes, unfortunately there was a contribution that I merged to support java-dsl backend.
And for whatever reason it requires this dependency.

Alternatively I think you may be able to locally just delete sub-tree that requires this. I am not 100% sure what to do with this as I am not really happy about such dependency; ideally it'd come via Maven (I don't object to non-java deps per se, as long as they integrate well).

So... that's the backstory. You can also download Mono support packages if you prefer, it's a one-time task at least.

@zapov
Copy link
Contributor

zapov commented Dec 1, 2016

To disable DSL compilation you can comment out annotation processor for CompiledJsonProcessor.

To avoid Mono dependency we can put generated code into the source... and recompile it on demand.

@cowtowncoder
Copy link
Owner

@zapov I think pre-generation would make sense here. I don't as much mind other build steps (as long as they are stable), but mono dependency is bit limiting for anyone who might just want to casually check things out.

@zapov
Copy link
Contributor

zapov commented Dec 3, 2016

I've created #7 so people can just run the project themselves.
If they want to change the model, they will have to fiddle with the setup somewhat :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants