Sounds reasonable. Could the main dropwizard repo utilize the "modules-parent" module as well or would you think that would unnecessarily complicate matters?
On Monday, June 3, 2019 at 8:32:15 PM UTC-5, Peter Stackle wrote: > > 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 > > -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-dev/ab7f18fc-01b4-4a98-951d-5a25396f6ebf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
