Given that PDFBox now already downloads dependencies from the net, one of my biggest points against Maven/Ivy is already moot. Switching to Maven now is not a big deal anymore. I still don't like builds that rely on possibly multiple external servers (besides the ASF's SVN server) to be online at the time of first build. There's not a worse impression of an open source tool downloaded the first time and it doesn't build.
On 11.09.2009 16:34:47 Jukka Zitting wrote: > Hi, > > I know we've touched this subject every know and then, but I'd like to > bring it up again: How would people feel about switching from Ant to > Maven as the main PDFBox build tool? > > Such a change would be quite beneficial to anyone who is already > familiar with the Maven conventions. Things like IDE and CI > integration would require next to no manual tweaking, and we could > easily leverage many of the best practices (source and javadoc jars, > built-in PGP signing, UTF-8 source encoding, standard LICENSE and > NOTICE file handling, etc.) encoded in the org.apache:apache parent > POMs. We also wouldn't need to worry about keeping the pom.xml file up > to date with changes in build.xml. > > WDYT? > > BR, > > Jukka Zitting Jeremias Maerki
