[ https://issues.apache.org/jira/browse/FOP-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003057#comment-16003057 ]
Chris Hannah commented on FOP-2705: ----------------------------------- [~ssteiner1] I attempted to build my app on my local machine and our Jenkins environment after deleting everything in the .m2/repository directory, and it wouldn't compile. Eclipse was giving me an error (Project read error) when it attempted to read my POM in my local development environment. > FOP 2.2 Doesn't Compile Due to Batik Dependencies > ------------------------------------------------- > > Key: FOP-2705 > URL: https://issues.apache.org/jira/browse/FOP-2705 > Project: FOP > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Chris Hannah > Priority: Critical > > I switched to FOP 2.2 so that I could get the fix for FOP-2525. When I > changed my FOP dependency to 2.2 my project would not compile. FOP 2.2 uses > version 1.9 for Batik dependencies. It appears that some Batik dependencies > reference a parent in their POM which does not exist. I resolved the issue in > my project by excluding all Batik dependencies for the FOP, and pulling in > version 1.8 for all Batik dependencies. I assume that using the Batik 1.9 > dependencies is desire, so, maybe this should be a BATIK issue instead. > I pulled the FOP 2.2 dependency from Maven Central. -- This message was sent by Atlassian JIRA (v6.3.15#6346)