Modules Parent POM?

[Peter Stackle]

Hey dropwizard-devs,

As Michael and I have been contributing some new, "non-core", modules that are part of the Dropwizard org, I see inconsistency between the other existing modules and even between some of the modules that the two of us just contributed. Internally, we had these modules as submodules of a multi-module project, so they were all able to inherit from a parent pom within the same project, similarly to how the multi-module "dropwizard/dropwizard" repo works today. While I think it does make sense to have these non-core modules be separate repos, I think having a parent POM that they all can inherit from would go a long way towards standardizing on a set of Maven plugin versions, execution configuration, and sign/release profiles. What do you think?

I'm happy to volunteer creating the parent POM for use by modules in the "io.dropwizard.modules" groupId, it would just require another repo created to hold it. Maybe call it "modules-parent"?

Thanks for your consideration,

Peter

[Nicholas Babcock]

Sounds reasonable. Could the main dropwizard repo utilize the "modules-parent" module as well or would you think that would unnecessarily complicate matters?

[Peter Stackle]

Sorry, I lost track of this thread for a while...

I hadn't considered that, but I think that assuming we are following the same process around building/releasing (which we should), then yeah, I think the main project and modules could all share a parent. In that case, I'll suggest a different name of "dropwizard-org-parent" so as not to conflict with the already existing "dropwizard-parent".