I would like to start a vote on merging from xmlgraphics/fop/branches/maven [1] to trunk [2]. Please respond by Wednesday, 03/16, 1700Z. Lack of a response will be interpreted as +0.
[1] http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/maven/ [2] http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ The following run without error (on my platform) using both JDK 1.6 and 1.7: - ant -f fop/build.xml clean all checkstyle findbugs - mvn clean install checkstyle:check findbugs:check -U I am using the following tool versions (with JDK 1.6 enabled): bash-3.2$ mvn -v Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T10:29:23-07:00) Maven home: /opt/local/share/java/maven32 Java version: 1.6.0_65, vendor: Apple Inc. Java home: /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac" bash-3.2$ ant -version Apache Ant(TM) version 1.9.6 compiled on June 29 2015 A Jenkins build project is running (without error) at [3], wherein both checkstyle and findbugs analyses are enabled by default. [3] https://builds.apache.org/job/xmlgraphics-fop-maven/ Notes: 1. the ant build is run from the fop subdirectory of [1]; 2. all build artifacts (fop, fop-sandbox, fop-servlet, fop-transcoder, fop-transcoder-allinone) have been verified for content; 3. source code is now distributed between fop-util, fop-events, and fop-core modules; this was needed to eliminate a circular dependency between fop and the generation of event infrastructure; i expect some further fine-tuning to occur here over time;
