I rolled it back to 4.2.0 because that is the version of avalon-framework-api that is included in the lib directory of fop's binary distribution (for both fop 1.0 and fop 1.1). I think the correct fix is either to add the 4.2.0 artifact to maven repo or to update the binary copy of that artifact to 4.3.1 that is included in fop/lib binary distribution [and also update the xmlgraphics-fop-pom-template.pom].
Since the first of the above options is easier to implement, perhaps someone could upload the 4.2.0 artifact to maven to fix this. G. On Sun, Dec 2, 2012 at 8:12 AM, Stephen More <stephen.m...@gmail.com> wrote: > fop 1.0 ( > http://repo.maven.apache.org/maven2/org/apache/xmlgraphics/fop/1.0/fop-1.0.pom) > has a dependency on org.apache.avalon.framework > - avalon-framework-api - 4.3.1 - works fine > > fop 1.1 ( > http://repo.maven.apache.org/maven2/org/apache/xmlgraphics/fop/1.1/fop-1.1.pom) > has a > dependency on org.apache.avalon.framework - avalon-framework-api - 4.2.0 > - broken > > But the repo only shows version 4.3.1 - > http://repo.maven.apache.org/maven2/org/apache/avalon/framework/avalon-framework-api/ > > Why was avalon rolled back to version 4.2.0 ? If version 4.2.0 is really > required then the artifact should be changed to avalon-framework-api - > avalon-framework-api > - 4.2.0 ( > http://repo.maven.apache.org/maven2/avalon-framework/avalon-framework-api/4.2.0/) > > > > > >