dropwizard / modules.dropwizard.io

Dropwizard modules directory

Dropwizard

Dropwizard is a sneaky way of making fast Java web applications.

It's a little bit of opinionated glue code which bangs together a set of libraries which have historically not sucked:

• Jetty for HTTP servin'.
• Jersey for REST modelin'.
• Jackson for JSON parsin' and generatin'.
• Logback for loggin'.
• Hibernate Validator for validatin'.
• Metrics for figurin' out what your application is doin' in production.
• JDBI and Hibernate for databasin'.
• Liquibase for migratin'.

Read more at dropwizard.io.

Want to contribute to Dropwizard?

Before working on the code, if you plan to contribute changes, please read the following CONTRIBUTING document.

Need help or found an issue?

When reporting an issue through the issue tracker on GitHub or sending an email to the Dropwizard User Google Group mailing list, please use the following guidelines:

• Check existing issues to see if it has been addressed already
• The version of Dropwizard you are using
• A short description of the issue you are experiencing and the expected outcome
• Description of how someone else can reproduce the problem
• Paste error output or logs in your issue or in a Gist. If pasting them in the GitHub issue, wrap it in three backticks: ``` so that it renders nicely
• Write a unit test to show the issue!

Sponsors

Dropwizard is generously supported by some companies with licenses and free accounts for their products.

JetBrains

JetBrains supports our open source project by sponsoring some All Products Packs within their Free Open Source License program.

modules.dropwizard.io's Issues

Add armeria-dropwizard

Made this

line/armeria#2236

Would like to see it listed as a module

How best to express version bounds?

I've noticed that there are several modules listed here that are compatible with newer versions of Dropwizard than the list indicates.

For example, I'm using https://github.com/tkrille/dropwizard-template-config with Dropwizard 1.0, but the page here lists "0.7, 0.8" for the version. When I first discovered this page, I skipped over the dropwizard-template-config project because I thought it wouldn't be compatible with newer DW versions.

Would it be okay for projects to list compatibility as something like "0.7+" to indicate there are no known issues with newer versions? Or is the expectation that package maintainers will periodically submit PRs here to update that their packages are compatible with newer dropwizard versions?

Why using master and gh-pages branch?

Looking at the PR #20 I wonder if I should have submitted the pull request for the gh-pages branch in the first place.

Thinking again: Why has this repo a master AND and gh-pages branch, why not a gh-pages branch only?

Some more information about making the gh-pages branch the default branch are available here http://www.xanthir.com/b4Zz0 and here http://oli.jp/2011/github-pages-workflow/