+1 my only concern is that you will need to restructure the current pom.xml files and later a cherry-pick from 7 to 6 (or vise versa) may not work as easy as now. but this is still manageable
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Sun, Sep 21, 2014 at 9:40 PM, Martijn Dashorst < [email protected]> wrote: > At work we use this maven plugin to enforce coding conventions for our > POMs: > > https://github.com/ferstl/pedantic-pom-enforcers > > While a major pain in the behinds, it enforces a single coding style > for Maven POMs, for example a definitive ordering of dependencies, > plugins, detecting duplicate code from dependencies, etc. > > It would be quite a hassle to initially introduce this plugin, and > every change you make (was that a song by the Police?) will probably > trigger one of the pedantic enforcer rules. > > In my experience at €day job the hassle is worth the pain. > > WDYT? I'm willing to add the plugin and make it work for our projects > in wicket 6 and 7 branches. > > Martijn > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com >
