DropWizard project with multiple modules?

[Rupert Smith]

Hi,

At the start of the DropWizard manual, it suggests splitting a project up into separate Maven modules:

https://dropwizard.github.io/dropwizard/manual/core.html

Modules called project-api, project-client and project-application.

I am quite a fan of splitting out a separate API module at least - it makes it simpler to version manage an API, and to diff the API for changes when writing release notes, as well as dealing with issues that will arise as a project grows in size, such as circular dependencies and so on.

Have anyone an example DropWizard project that I can look at that follows this recommended structure for the build? All examples I have found on GitHub so far just have a single module and one pom.xml. Thanks for your help.

Rupert

[Carlo Barbara]

The code is a bit stale, but the it shows how to organize the poms.

https://github.com/cab222/choco

--
You received this message because you are subscribed to the Google Groups "dropwizard-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-us...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jacek Furmankiewicz]

We do it in Gradle, no issues.

Not a big fan of Maven any more, a bit too much of XML for even the tiniest thing.

[Rupert Smith]

On Sunday, July 20, 2014 2:08:49 PM UTC+1, Jacek Furmankiewicz wrote:

We do it in Gradle, no issues.

Not a big fan of Maven any more, a bit too much of XML for even the tiniest thing.

Then disregard that I mentioned Maven. The real question is, is there an example of how to structure a DropWizard project into modules, regardless of build system? The question is more about architectural layering, than build systems. Thanks.

Rupert