-
Notifications
You must be signed in to change notification settings - Fork 5
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
Missing resource #2
Comments
@KnowledgeGarden Can you check whether you use the latest version? I just checked and the handlebars dependency is provided via the vertx-web-templ-handlebars. Which JVM are you using? |
1.8.172. Bringing down master again, building it in eclipse because Server.java does not come down with localhost, 8080, false vert for the client, AND, the pom file is missing the artifact found here: https://mvnrepository.com/artifact/com.github.jknack/handlebars/4.0.6, it is now running. |
It is now my intention to use that codebase as a framework for a different UI. |
Updated the pom to the latest Mesh version; the Server is now broken in terms of WebRootResponse now becoming MeshWebRootResponse which, when changed, propagates compile errors in handleImages due to resolvePath(path).subscribe(response -- that response doesn't show the download APIs |
@KnowledgeGarden I updated the master branch. The example will now also work with the latest version of Gentics Mesh. |
Had to add the com.github.jknack.handlebars reference to pom.xml to get it to boot (running inside Eclipse). Boots, then this: FWIW, all runs with this example show this in the log (console) |
INFO: Connecting to Gentics Mesh..
Jun 06, 2018 9:14:20 AM io.vertx.core.impl.DeploymentManager
SEVERE: com/github/jknack/handlebars/io/TemplateLoader
java.lang.NoClassDefFoundError: com/github/jknack/handlebars/io/TemplateLoader
at io.vertx.ext.web.templ.HandlebarsTemplateEngine.create(HandlebarsTemplateEngine.java:51)
at com.gentics.mesh.example.Server.start(Server.java:142)
Adding this to the pom.xml solved it:
com.github.jknack
handlebars
4.0.7
but that's not the end of the story; I'll post a new issue which may or may not be related to this one.
The text was updated successfully, but these errors were encountered: