avalon 4.2.0 artifact is already loaded in repo, it just has a different
group id.
Changing fop-1.1.pom from:
<dependency>
<groupId>org.apache.avalon.framework</groupId>
<artifactId>avalon-framework-api</artifactId>
<version>4.2.0</version>
</dependency>
<dependency>
<groupId>org.apache.avalon.framework</groupId>
<artifactId>avalon-framework-impl</artifactId>
<version>4.2.0</version>
</dependency>
to
<dependency>
<groupId>avalon-framework</groupId>
<artifactId>avalon-framework-api</artifactId>
<version>4.2.0</version>
</dependency>
<dependency>
<groupId>avalon-framework</groupId>
<artifactId>avalon-framework-impl</artifactId>
<version>4.2.0</version>
</dependency>
should resolve the issue. The maintainers of the repo do not want to the
see the same artifact loaded twice with 2 different name spaces. Since the
pom has already been released I guess a new pom 1.1.1 would have to be
pushed out with the fix.
-Stephen More
On Sun, Dec 2, 2012 at 11:26 AM, Glenn Adams <[email protected]> wrote:
> to implement, perhaps someone could upload the 4.2.0 artifact to maven to
> fix this.
