From: Stefan B. <bo...@ap...> - 2015-01-03 11:42:42
|
On 2015-01-03, Eric Siegerman wrote: > [I've pasted back in a few lines from Harald's post that Stefan snipped] sorry :-) > On 12/26/2014 06:12 AM, Stefan Bodewig wrote: >> On 2014-12-24, Harald Brabenetz wrote: >>> The advances would be the following >>> - Modern IDEs can read the pom.xml and configure the Projects > automatically (no manual selection where the source folders or the > libraries are). >>> - You doesn't need to check-in libraries like hamcrest or junit >>> - It's much easier to deploy to the maven central repo (with the > maven-release-plugin and some configurations for the Sonatype's OSSRH) >> I guess what I'm asking is: can I be sure there will be a result that >> goes beyond replacing a build system I like with one I don't like :-) > Instead of switching completely over to Maven, why not use a > hybrid approach? Yes, that would certainly be an option, but I'm not sure maintaining two different build systems (for example when a new version of JUnit is released) and fighting against Maven conventions will be worth it. Also, I'm not sure this really solves the IDE point. Developers still had to tell their IDE where to look for the sources. At least I think they'd have to. I've tried to capture the discusion here <https://github.com/xmlunit/xmlunit/wiki/Building-XMLUnit#discussion> Stefan |