来自itext的jasper-reports中的依赖性错误 [英] Dependency error in jasper-reports from itext

问题描述

从昨天开始，由于iText jar，我在使用maven进行编译时出现问题。
我的项目依赖于jasperreports-2.0.1，它依赖于itext-1.02b或更高。

From yesterday I have problems compiling with maven because of iText jar. My project has a dependency of jasperreports-2.0.1 that depends on itext-1.02b or higher.

<dependency>
    <groupId>com.lowagie</groupId>
    <artifactId>itext</artifactId>
    <version>[1.02b,)</version>
    <scope>compile</scope>
</dependency>

这是maven中的日志错误：

That is the log error in maven:

Failed to collect dependencies for [jasperreports:jasperreports:jar:2.0.1 (compile)]: Failed to read artifact descriptor for com.lowagie:itext:jar:4.2.2: Could not transfer artifact com.itextpdf:itextpdf:pom:4.2.2 from/to jaspersoft (http://www.jasperforge.org/maven2): Access denied to http://www.jasperforge.org/maven2/com/itextpdf/itextpdf/4.2.2/itextpdf-4.2.2.pom. Error code 403, Forbidden -> [Help 1] 

我看到这里来自Amedee Van Gasse的评论说明了一个没有jar的4.2.2版本。

I see here a comment from Amedee Van Gasse that says something about a 4.2.2 version with no jar.

为什么1.02b版本附加到4.2.2？

Why does the 1.02b version attach to 4.2.2?

编辑：
Jasper-reports使用开放版本范围：

Jasper-reports uses an open version range:

[1.02b，]

[1.02b,)

这个范围对maven采取库最新版本。

This range says to maven to take the library latest version.

使用更新从iText添加新版本Pom没有jar并编辑maven-central的maven-metadata到no-jar版本根据最新的com.lowagie库将编译崩溃到所有jar。

With the update from iText adding new version Pom with no jar and editting the maven-metadata of maven-central to that no-jar version crashes the compilation to all jar depending form latest com.lowagie library.

在本地更新您的maven-metadata-central.xml（以及其他元数据，如果您的公司拥有自己的nexus.public）来自... m2 \repository \ com \\ glowagie\itext
就可以了。暂时解决方案直到iText更新元数据或所有依赖于它的公司的最新版本更新它的pom

Updating locally your maven-metadata-central.xml (and other metadata if your company has it's own nexus.public) from ...m2\repository\com\lowagie\itext to that works. Temporally solucion until iText updates the metadata or ALL companies that has dependencies for it's latest version updates it's pom

<metadata modelVersion="1.1.0">
  <groupId>com.lowagie</groupId>
  <artifactId>itext</artifactId>
  <versioning>
    <latest>4.2.1</latest>
    <release>4.2.1</release>
    <versions>
      <version>0.99</version>
      <version>1.1.4</version>
      <version>1.02b</version>
      <version>1.2.3</version>
      <version>1.3</version>
      <version>1.3.1</version>
      <version>1.4</version>
      <version>1.4.8</version>
      <version>2.0.1</version>
      <version>2.0.6</version>
      <version>2.0.7</version>
      <version>2.0.8</version>
      <version>2.1.0</version>
      <version>2.1.2</version>
      <version>2.1.3</version>
      <version>2.1.4</version>
      <version>2.1.5</version>
      <version>2.1.7</version>
      <version>4.2.0</version>
      <version>4.2.1</version>
    </versions>
    <lastUpdated>20150709153501</lastUpdated>
  </versioning>
</metadata>

推荐答案

一个更简单的解决方案可能是升级到更新的版本 jasperreports 。版本 6.1.0 依赖于iText：

A much simpler solution may be to upgrade to a newer version of jasperreports. Version 6.1.0 has this dependency on iText:

<dependency>
    <groupId>com.lowagie</groupId>
    <artifactId>itext</artifactId>
    <version>2.1.7.js2</version>
    <scope>compile</scope>
</dependency>

对iText不再有浮动依赖，而且它是为jasperreports定制的版本！

No more "floating" dependency on iText, and it's a version that's custom made for jasperreports!

请参阅 http://mvnrepository.com/ artifact / net.sf.jasperreports / jasperreports / 6.1.0 表示完整的 pom.xml 。

这篇关于来自itext的jasper-reports中的依赖性错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！