Hi Justin, thank you for the pointing to cause of my concerns, it is a WET solution. Actually, I was not able to say why I'm not sure about how I write new slides, now I know. Thank you.
Write Everything Twice means newcomers need to Read Everything Twite. I've spent a couple of hours to understand how I can build my own pom for Apache Ignite slides. I'm not an expert in Maven, so somebody can do it faster than me. I suppose some parent pom, where "magic" is hidden, could be easier to understand. DRY: I can copy-paste some (short) POM.xml, which was contributed earlier; and add my slides name and some specific settings - that's it. WET: In the current approach, I have to copy-paste (long) XML config, while trying to find out why it is here, why it is there. Sincerely, Dmitriy Pavlov пн, 27 мая 2019 г. в 19:30, Lars Francke <[email protected]>: > > > > 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 >
