在不同 Eclipse 版本之间移动插件
我需要将几个插件安装到在远程 64 位 Linux 机器上运行的 eclipse。
我尝试将必要的插件复制到远程计算机上的插件和功能文件夹中，但它似乎不起作用。
我现在想尝试的方法是使用所有插件设置新的 Eclipse 安装并替换整个 eclipse 文件夹。
但当我这样做时，我意识到我必须使用 32 位 Linux 和 Eclipse。是否可以安装 32 位 Eclipse 并将插件和功能移动到远程计算机？ 我还需要考虑其他事情吗？ 您能推荐任何其他对我有帮助的方法吗？
更新： 问题是我无法在远程计算机上启动 eclipse。我可以通过 ssh 访问它，但不能运行 eclipse 并通过向导安装插件。 我也没有64位linux来准备一个完整的eclipse，我可以简单地复制。 所以我的意思是我必须准备一个 Eclipse 安装或者只是插件文件夹并将其从我的 32 位体系结构移动到 64 位体系结构。
我可以下载当前的 eclipse 文件夹，但无法运行它。当我尝试用 ubuntu 启动它时，没有任何反应。我相信这是因为它是 64 位版本，而我有 32 位架构。
I need to install several plugins to an eclipse that is running on a remote 64bit Linux machine.
I tried copying the neccesary plugins to the plugins and feature folder on the remote machine but it did not seem to work.
The approach I wanted to try out now was setting up a new Eclipse installation with all plugins and replacing the whole eclipse folder.
But as I am doing this I realized that I have to use a 32 bit Linux and Eclipse. Is it possible to install 32bit Eclipse and just move the plugins and features to the remote machine?
Do I need to consider other things?
Can you recommend any other approach that would help me?
UPDATE:
The problem is that I cannot just start eclipse on the remote machine. I can access it via ssh but not run eclipse and install plugins via the wizards.
I also have no 64bit linux to prepare a complete eclipse that I can simply copy.
So what I meant is that I have to prepare either an eclipse installation or maybe just plugin folder and move that from my 32bit architecture to the 64bit one.
I can download the current eclipse folder but I cannot run it. When I try to start it with ubuntu nothing happens. I believe it is because its a 64bit version and I got 32 bit architecture.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
不要这样做。不仅有许多带有本机编译片段的插件（32 位与 64 位不同），而且在最近的版本中，Eclipse 甚至不会注册简单插入的功能和插件。您应该显式安装插件除非您要在具有兼容架构的计算机之间移动整个安装。
Don't do this. Not only are there are a number of plugins with native-compiled fragments (different for 32-bit vs 64-bit), but in recent versions, Eclipse will not even register features and plugins that are simply dropped in. You should install plugins explicitly unless you are moving the entire installation between machines with compatible architectures.
如果没有某种能够进行完整 CPU 模拟的虚拟化软件，您就无法在 32 位系统上运行 64 位二进制文件。 VMWare、VirtualPC 等...不要这样做。他们虚拟化系统，但不虚拟化 CPU。
相反：如果操作系统（和处理器）支持这样的东西，那么 64 位 cpu 上的 32 位二进制文件通常是可能的。
You can't run a 64bit binary on a 32bit system without some kind of virtualization software that does a complete CPU emulation. VMWare, VirtualPC, etc... don't do this. They virtualize the system, but not the CPU.
The other way around: a 32bit binary on a 64bit cpu, is generally possible, if the OS (and processor) supports such things.
我认为这是可行的。
架构不应该是问题。除非插件包含通过 JNI 调用的 DLL 或 .so 库，但例子很少（swt 是一个例子，但例子很少）。
事实上，你拥有 OS/arch/GUI 特定版本的 eclipse 的原因不是 java 代码，而是本机启动器（windows 和 SWT 上的 eclipse.exe），其余的都可以在一台机器上来回运行对于另一个，无论架构、操作系统或 windows 管理器如何。
然而，将 jar 放在 eclipse 的插件目录中不再是安装插件的推荐方法（从 3.3 开始？）。它可能会起作用，但不能保证。
要安装缺少的插件，您应该从 eclipse 本身下载它们（帮助 => 安装新软件...）。如果您告诉我们您遇到问题的具体插件，我们也许能够更准确地为您提供帮助。
前进的最佳方法是列出源计算机上的所有插件（来自 eclipse (help => about) 并查看 arch/os/gui 中具有特定提示的名称。所有这些都无法复制。所有休息应该是安全的。
正如我所说，要小心 swt。如果您决定使用 JavaHL，Subclipse 具有 JNI 相关配置。还有一些“虚假”插件，例如 xmlSpy 等，它们注意到的不仅仅是 JNI 适配器，但这些并不是主流。
I think this is feasible.
The architecture should not be the problem. Unless the plugins contain DLLs or .so libraries invoked through JNI but there are very few examples (swt is one example but there are very few of them).
As a matter of fact, the reason why you have OS/arch/GUI specific versions of eclipse is not the java code but the native launcher (eclipse.exe on windows and SWT), all the rest can go bck and forth from one machine to the other, regardless of the arch, the os or the wondows manager.
However, dropping jars in the plugin directory of eclipse is not the recommended way of installing plugins any more (since 3.3 ?). It might work but there is no guarantee.
To install the missing plugins you should download them from eclipse itself (help => install new software...). If you tell us the specific plugins you have problem with, we might be able to help you more precisely.
The best way to go forward is to list all the plugins on the source machine (either from eclipse (help => about) and look at names having specific hints at arch/os/gui. All these cannot be copied over. All the rest should be safe.
As I said, beware of swt. Subclipse has a JNI dependent configuration if you decide to use JavaHL. And there are also "false" plugins such as xmlSpy etc who are noting more than JNI adapters but these are not mainstream.