We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(4)
在 Maven 中心,最新版本是 4.0.1:
http://repo2.maven.org/maven2/net/sf/jasperreports/ jasperreports/
注意 groupid net.sf.jasperreports
In Maven central the latest version is 4.0.1:
http://repo2.maven.org/maven2/net/sf/jasperreports/jasperreports/
Note the groupid net.sf.jasperreports
在 v5.1.0 中遇到了同样的问题,并使用以下命令使其正常工作:
Faced same issue with v5.1.0 and got it working using:
这是最新版本:
还有一个非常好的插件可以自动将 jrxml 文件编译为 jasper。只需将以下内容放入 src/main/jasperreports
源中的 pom 和 jrxml 文件中: http://www.mojohaus.org/jasperreports-maven-plugin/usage.html
This is the latest version:
There is also a pretty nice plugin to compile jrxml files to jasper automatically. Just put the following in your pom and your jrxml files in src/main/jasperreports
Source: http://www.mojohaus.org/jasperreports-maven-plugin/usage.html
您可以在以下存储库中找到这些工件:
http://repository.jboss.org/nexus/content/groups/public-jboss/net/sf/jasperreports/jasperreports/
http://mirrors.ibiblio.org/maven2/net/sf/jasperreports/jasperreports/
http://repo1.maven.org/maven2/net/sf/jasperreports/jasperreports/
当然其他存储库也包含这些工件。
顺便说一句,如果您使用 jasper reports
并且您在代理后面或在商业环境中使用 Maven Enterprise Repository,它会给您带来一些麻烦,因为它定义了自己的存储库列表,这几乎是不行的。我引用pom的代码:
您的maven客户端将尝试直接访问这些存储库。
为了避免这个问题,请查看此票证 如何配置 Maven 来忽略 POM 文件中指定的存储库?
You find the artifacts in the following repositories:
http://repository.jboss.org/nexus/content/groups/public-jboss/net/sf/jasperreports/jasperreports/
http://mirrors.ibiblio.org/maven2/net/sf/jasperreports/jasperreports/
http://repo1.maven.org/maven2/net/sf/jasperreports/jasperreports/
Surely other repositories contain those artifacts too.
By the way, if you use the jasper reports
and you are behind a proxy or use in a commercial environment a Maven Enterprise Repository it will give you some troubles, as it defines its own list of repositories, which is almost a no-go. I quote the code of the pom:
Your maven client will try to access those repositories directly.
To avoid this matter have a look at this ticket How do you configure maven to ignore repositories specified in POM files?