ingenieux / jbake-maven-plugin Goto Github PK

To bootstrap a jbake maven site, it would be really useful to have a jbake:initiale goal ensuring required files exist in a correct fashion.

Such as Freemarker, Markdown etc. As they are now marked as optional in JBake's pom.xml

Would be ideal if we could get another release with these added out once I've got a bug fix release out for JBake (v2.3.2).

hello
I'm using the 0.0.9 version of the jbake maven plugin to try it out for some documentation. When I build with the goal jbake.watch or jbake.inline, I get the error about suitable rendering engines. I added the thymeleaf dependencies into my pom.xml, and I've looked at the parser/Engines.java internal documentation, but I'm still a little unclear on how to set this up. Thank you.

Hi,
I'm using the jbake-maven-plugin 0.0.8, thanks for your work !

When launching the target jbake:inline everything gets generated correctly and the plugins wait for a change. Once a change is made the execution stops with the following error:

[INFO] Running. Enter a blank line to finish. Anything else forces re-rendering.
[INFO] Refreshing
[INFO] Oops
com.orientechnologies.orient.core.exception.OConfigurationException: Error on opening database: the engine 'memory' was not found. URL was: memory:cache. Registered engines are: []
at com.orientechnologies.orient.core.Orient.loadStorage(Orient.java:208)
at com.orientechnologies.orient.core.db.raw.ODatabaseRaw.exists(ODatabaseRaw.java:206)
at com.orientechnologies.orient.core.db.ODatabaseWrapperAbstract.exists(ODatabaseWrapperAbstract.java:65)
at com.orientechnologies.orient.core.db.ODatabaseWrapperAbstract.exists(ODatabaseWrapperAbstract.java:65)
at org.jbake.app.DBUtil.createDB(DBUtil.java:25)
at org.jbake.app.Oven.bake(Oven.java:121)
at br.com.ingenieux.mojo.jbake.GenerateMojo.reRender(GenerateMojo.java:83)
at br.com.ingenieux.mojo.jbake.WatchMojo.executeInternal(WatchMojo.java:88)
at br.com.ingenieux.mojo.jbake.GenerateMojo.execute(GenerateMojo.java:58)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO] Oops
org.apache.maven.plugin.MojoExecutionException: Failure when running:
at br.com.ingenieux.mojo.jbake.GenerateMojo.reRender(GenerateMojo.java:87)
at br.com.ingenieux.mojo.jbake.WatchMojo.executeInternal(WatchMojo.java:88)
at br.com.ingenieux.mojo.jbake.GenerateMojo.execute(GenerateMojo.java:58)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: com.orientechnologies.orient.core.exception.OConfigurationException: Error on opening database: the engine 'memory' was not found. URL was: memory:cache. Registered engines are: []
at com.orientechnologies.orient.core.Orient.loadStorage(Orient.java:208)
at com.orientechnologies.orient.core.db.raw.ODatabaseRaw.exists(ODatabaseRaw.java:206)
at com.orientechnologies.orient.core.db.ODatabaseWrapperAbstract.exists(ODatabaseWrapperAbstract.java:65)
at com.orientechnologies.orient.core.db.ODatabaseWrapperAbstract.exists(ODatabaseWrapperAbstract.java:65)
at org.jbake.app.DBUtil.createDB(DBUtil.java:25)
at org.jbake.app.Oven.bake(Oven.java:121)
at br.com.ingenieux.mojo.jbake.GenerateMojo.reRender(GenerateMojo.java:83)
... 23 more
[INFO] Finishing
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.333 s
[INFO] Finished at: 2014-11-27T10:36:23+01:00
[INFO] Final Memory: 15M/340M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal br.com.ingenieux:jbake-maven-plugin:0.0.8:inline (default-cli) on project site: Oops: Failure when running: Error on opening database: the engine 'memory' was not found. URL was: memory:cache. Registered engines are: [] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Everything in the code and pom already supports that (except you could add the Pegdown and Asciidoc dependencies to the pom.xml, too). Version 2.4.0 gives more support for configuring the Markdown to output format transformation

When I use jbake:watch, how do I open the page? I tried 8080 and 8820 but no luck?

Can JBake be integrated into Maven in the same way as the Maven site plugin, to generate the Maven reports such as the dependency management, mailing lists, team page, etc?

The crashub.org website uses the jbake-maven-plugin and the same configuration is repeated twice at the moment, once in the pom.xml properties and once in the jbake.properties file:

Currently the site project does have a jbake.properties that contains:

crash.version=1.2.8
crash.next.version=1.3.0-beta15

At the same time, in the pom.xml there is also the same configuration :

So if the plugin configuration could allow to do something like:

That would allow to keep one configuration and honour the DRY principle.

Hey I just saw that in 0.2.0 the JBake properties can be overridden in the plugin execution but I can't find that version on maven central: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22br.com.ingenieux%22%20AND%20a%3A%22jbake-maven-plugin%22

Any chance you can publish that and maybe the other releases on maven central too?

idea would be to add dependencies and target/classes to be able to use in gsp some utility developped in src/main/java or a dependency (these ones can be added to the plugin but when using some utility from src/main/java in a dedicated module it is a big copy/paste we can avoid).

Opening tag does not match closing tag