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

assertion failed: Incoherence: dynverTagPrefix=v vs dynverVTagPrefix=false #169

Closed
ignasi35 opened this issue Jun 30, 2020 · 3 comments · Fixed by #170
Closed

assertion failed: Incoherence: dynverTagPrefix=v vs dynverVTagPrefix=false #169

ignasi35 opened this issue Jun 30, 2020 · 3 comments · Fixed by #170
Assignees

Comments

@ignasi35
Copy link
Contributor

Upgrading from 4.0.0 to 4.1.0 a project with the setting:

dynverVTagPrefix in ThisBuild := false

causes the project to not load with the error:


[info] loading settings for project twirl from build.sbt ...
[error] java.lang.AssertionError: assertion failed: Incoherence: dynverTagPrefix=v vs dynverVTagPrefix=false
[error] Use 'last' for the full log.
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?

(see for example https://travis-ci.com/github/playframework/twirl/jobs/355362477)

The workaround is to opt out of the (old) dynverVTagPrefix and, instead, set dynverTagPrefix="". See the release notes.

@ignasi35
Copy link
Contributor Author

Hmm, sometimes the error is not printed? (https://travis-ci.com/github/lagom/lagom/jobs/355355692#L267)

@dwijnand
Copy link
Member

That's my bad. I really should've tested that check. Of course it's going to throw... :-/

I'll try to fix this tomorrow.

@ignasi35
Copy link
Contributor Author

ignasi35 commented Jul 1, 2020

Thanks @dwijnand for the quick fix.

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

Successfully merging a pull request may close this issue.

2 participants