From: Eric S. <pub...@da...> - 2015-01-03 01:42:27
|
[I've pasted back in a few lines from Harald's post that Stefan snipped] 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? Keep Ant, but write a minimal POM for consumption by the general public. It could specify the external dependencies, but delegate to Ant and build.xml for the actual build. [1] That way, you (i.e. Stefan) get the first of the advantages that are claimed for Maven -- and the second one too, if you want it, with a bit of finagling. But: - you can keep using the build system you prefer - you don't have to completely reorganize your project structure - you don't have to wrestle with the release plugin [1] For calling out to Ant, one option is: http://maven.apache.org/plugins/maven-antrun-plugin/ Eric |