We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Create a /tests/test-war-quickstart that tests the quickstart facility of jetty.
/tests/test-war-quickstart
The sample project should be sufficiently complex. Perhaps either the spring petclinic, or the cdi/weld petclinic.
The text was updated successfully, but these errors were encountered:
Since the existing spring petclinic is broken (due to Dandelion bug) we'll have to build our own spring petclinic.
We could include a known slow (to scan) jar file org.webjars:extjs:5.1.0.jar to be sure that the quickstart actually works.
org.webjars:extjs:5.1.0.jar
I think we'll have to dig into the logs to test if this startup was truly "quick" or not.
Sorry, something went wrong.
Issue #33 is also a spring petclinic testcase (non-quickstart version)
I think this is only useful to test if the gcloud sdk offers quickstart as an option during the deploy step. Is this the case @meltsufin or @aslo ?
As quickstart support is not directly supported by the SDK, let's close this one for now.
No branches or pull requests
Create a
/tests/test-war-quickstart
that tests the quickstart facility of jetty.The sample project should be sufficiently complex. Perhaps either the spring petclinic, or the cdi/weld petclinic.
The text was updated successfully, but these errors were encountered: