Look at standardising on HTTP server used in core & Maven plugin

[jonbullock]

Is it worth standardising? What's the benefits?

Options:
http://winstone.sourceforge.net/
http://www.eclipse.org/jetty/
http://undertow.io/

[aldrinleal]

Not worth, but I believe its better if JBake keeps as a engine focused on rendering, and the plugin (or an additional tool) support this functionality

A key aspect for me is to be able to allow custom file types and (optionally) deployment pipelines, so, say, if I ever have to rewrite html content to point to a CDN, or even deploy, it could come easier.

[jonbullock]

It's useful for local testing without the need for additional tools such as Maven/Gradle, especially for users who don't those kind of tools installed by default, such as designers or more front end developers. I don't want to exclude these users from using JBake.

[aldrinleal]

For Designers and Frontend, folks recommend using Vagrant. I believe
building a Vagrant box with the maven (+ the plugin) would be nice :)

-- Aldrin Leal, aldrin@leal.eng.br
Master your EC2-fu! Get the latest ekaterminal public beta
http://www.ingenieux.com.br/products/ekaterminal/

On Tue, Feb 25, 2014 at 9:59 AM, Jonathan Bullock
notifications@github.qkg1.topwrote:

It's useful for local testing without the need for additional tools such
as Maven/Gradle, especially for users who don't those kind of tools
installed by default, such as designers or more front end developers. I
don't want to exclude these users from using JBake.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/41#issuecomment-36004580
.

[gilbertoca]

I came from Jekyll because of this feature, just install JBake and you (users/designers/frontend) are ready. No need to sudo here, sudo there or ANYTHING ELSE that obstruct you from see/work at what are you doing as blogger or designer.

PS.:
I would choose one that has fewer dependencies since it will render just static resources.

[jonbullock]

Thanks for the feedback Gilberto.

[wadechandler]

I see this as super valuable myself. I think if one would like to access the server because they need to use full paths to resources for various reasons, then a server running the site as a "top level" site, is the only way. Just viewing the static site without a server won't work in that case. So, if it can be an optional feature, which it could be with a command, then it should be useful and out of the way. If it can download the server artifact at runtime, then all the better, as it will only need it when one uses it.

[msgilligan]

Another option (for JDK 18 and later) is the simple, static web server built in to Java: https://openjdk.org/jeps/408