quickstart support?

[gregw]

Should quickstart be supported by default, or documented as a desirable feature.
Testing done in #8 using quickstart and/or annotations

[meltsufin]

What would implementing quickstart support entail? Is it just turning on the quickstart module? Does the app have to be built a different way to work with quickstart?

[gregw]

It is a module that needs to be turned on, plus the webapp needs to be built with a quickstart-war file.

So if there is going to be SDK support to deploy webapps to this image, it is a good option to have to save CPUs. If there is no SDK support, then it is something the users can turn on themselves and we should just prepare an example project and documentation.

[janbartel]

See issue #25 also.

[ludoch]

pure jetty-runtime does not have prebaked SDK support.
The user could modify her pom.xml to enable quickstart?

On Thu, Sep 15, 2016 at 4:06 PM, Jan Bartel [email protected]
wrote:

See issue #25
#25 also.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE4zUGSz3JFqBBvkIvsx_IULfNGvnaVks5qqc-DgaJpZM4J3hvw
.

[gregw]

To use quickstart a user would need to:

• add a quickstart-web.xml to WEB-INF
• enable the quickstart module on the jetty base.

Both are simple to do, so I think this is more a documentation/example issue rather than a coded feature.

[meltsufin]

Would they need to build a custom runtime to enable the quickstart module?

[gregw]

@meltsufin, yes they would need to provide their own Dockerfile that enables the quickstart module.

[joakime]

the regression testing could handle that in /jetty-runtime/ easily enough.

Each /tests/webapp/test-war-*/ has its own docker.

To do:

• Add new test project
• Dockerfile updated to add the quickstart module to the jetty.base
• test-war-quickstart has maven plugin that builds out the quickstart-web.xml
• deploy and integration testing as usual