如何将com.lowagie itext格式从2.1.7迁移到4.2.0 [英] How to migrate com.lowagie itext form 2.1.7 to 4.2.0

查看:173
本文介绍了如何将com.lowagie itext格式从2.1.7迁移到4.2.0的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在处理的应用程序使用的是com.lowagie itext 2.x的旧版本,现在我想将其移至4.x的较高版本,但是好像几个包都被重命名/删除了,等等.我想问问是否有人迁移到4.x?如果是这样,任何建议都将是很棒的.预先感谢

The application I'm working on is using older versions of com.lowagie itext 2.x, now i want to move that to upper version to 4.x, but it looks like several packages are being renamed/removed etc.. I would like to ask if anyone did a migration to 4.x ? If so any suggestions would be great. Thanks in advance

推荐答案

从来没有iText 4.2.0.如果找到声称是iText 4.2.0的版本,则不应使用它,因为它违反了开源准则.这篇文章对此进行了解释:我的Maven构建已损坏,我该怎么办? 是对此StackOverflow问题的答案:

There has never been an iText 4.2.0. If you find a version that claims to be iText 4.2.0, then you shouldn't use it because it's in violation with the guidelines of open source. This is explained in this post: My Maven build is broken, what should I do? which was an answer to this StackOverflow question: com.lowagie.itext version 4.2.2 missing jar file in MVNrepository

我引用:

2.1.75.0.0之间的其他任何版本的iText,例如4.2.04.2.1,是其他公司的货叉.根据 Apache将工件上传到中央存储库的指南,那些公司应该 使用了另一个groupId,因为Apache FAQ明确指出:

Any other versions of iText between 2.1.7 and 5.0.0, like 4.2.0 and 4.2.1, are forks by other companies. According to Apache's Guide to uploading artifacts to the Central Repository, those companies should have used a different groupId, as the Apache FAQ clearly states:

我在foo.com上开发了一个foo项目的补丁版本, 我应该使用groupId吗?

I have a patched version of the foo project developed at foo.com, what groupId should I use?

修补/修改第三方项目时, 该补丁版本将成为您的项目,因此应该 在您控制的groupId下分发,就像您将拥有的任何项目一样 开发,永远不在com.foo下.请参阅上述注意事项 groupId.

When you patch / modify a third party project, that patched version becomes your project and therefore should be distributed under a groupId you control as any project you would have developed, never under com.foo. See above considerations about groupId.

劫持"公司的公司所造成的情况 com.lowagie groupId造成了一个问题,您可能会无意间 引入侵犯版权或商标权的软件 第三方(或更糟)进入您的项目.为了阻止这种情况,iText具有 重新获得了对com.lowagie的控制权,我们已确保没有 会再发生.

The situation created by the companies that "hijacked" the com.lowagie groupId created a problem where you could inadvertently introduce software that the infringes the copyright or trademarks of third parties (or worse) into your project. To stop this, iText has regained control over com.lowagie and we have made sure that this no longer happens.

如果您决定使用旧版本的iText,可以在以下位置进行: 您自己承担风险.

If you decide to stick with an old version of iText, you can do so at your own risk.

2.1.7(2009年7月)是iText Group NV公司(或其合法前身)发布的最新iText版本,带有com.lowagie groupId. iText Group NV公司发布的下一个iText版本是5.0.0,带有com.itextpdf groupId,这意味着它与您的当前代码二进制不兼容.

2.1.7 (July 2009) was the last version of iText released by the company iText Group NV (or its legal predecessor), with the com.lowagie groupId. The next version of iText, released by the company iText Group NV, was version 5.0.0, with the com.itextpdf groupId, which means it's binary incompatible with your current code.

在您的问题中,您正在询问如何从正式版本转为正式版本(法律和技术原因)到不受支持的版本,该版本违反了开源社区的准则和规则. iText 4.2.0 gork ,它是iText 2.1.7的一个版本,其中 G od O nly R eally K 了解其中的内容.问题如何将com.lowagie iText从2.1.7迁移到4.2.0 的唯一正确答案是:您不要!你就是不!

In your question, you are asking how to move from an official version (that should no longer be used in a commercial context for legal and technical reasons) to an unsupported version that is in violations with the guidelines and rules of the open source community. iText 4.2.0 is a gork, it's a version of iText 2.1.7 of which God Only Really Knows what's inside. The only correct answer to the question How to migrate com.lowagie iText from 2.1.7 to 4.2.0 is: You dont! You just don't!

您可以迁移到iText 5.5.13,它是iText 5系列的最新版本.那应该很容易.主要是将com.lowagie更改为com.itextpdf的问题.

You can migrate to iText 5.5.13, which is the latest version in the iText 5 series. That should be fairly easy. It's mostly a matter of changing com.lowagie into com.itextpdf.

您还可以迁移到iText 7.1.1,这是全新的iText版本.迁移到该版本需要更多编程,因为iText 7是iText的全新版本(从头开始重建).根据客户要求对体系结构进行了更改,因此我们可以支持无法插入iText 5的功能(例如:支持印度语,如Devanagari和Tamil).

You can also migrate to iText 7.1.1, which is the all new iText version. Migrating to that version requires more programming as iText 7 is a completely new version of iText (rebuilt from scratch). The architecture was changed based on customer requests, so that we can support features that couldn't be inserted into iText 5 (for instance: support for Indic languages such as Devanagari and Tamil).

有关您的信息:我是您写com.lowagie时所指的Lowagie.

For your info: I am the Lowagie you refer to when you write com.lowagie.

这篇关于如何将com.lowagie itext格式从2.1.7迁移到4.2.0的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆