> > Take care that you not solving a problem that we don’t really have yet. > Premature optimisation and all that. Remember than many people who consume > our content may not be maven experts and we want it to be simple for them > to use. I’m all for DRY in code, but WET in test is better and easier to > understand and that may also apply to the build files here and the audience > we have. >
In my opinion, we already have (and had) this problem. If all the things we produce had a parent pom we would only need to fix things once. Now when Sönke fixed the filename issue he had to do it twice but that'll grow soon. Cheers, Lars
