Eclipse不会从目标平台下载相同版本的最新jar [英] Eclipse does not download latest jar of the same version from the target platform

问题描述

我的Eclipse IDE（Indigo V3.7.2）中有一个奇怪的问题。我们使用托管在服务器上的目标平台，该平台是使用b3聚合过程构建的p2存储库。我们从不同的团队获得某些组件和功能。每次交付插件时，版本号保持不变（例如myjar_v1.0.0.jar）（当然尺寸是不同的）。我们在远程服务器上更新这些插件。此更新后，问题是，如果我使用现有的工作区，我看到我的代码中的编译问题，因为最新的jar没有从目标平台下载。
由于相同的版本和名称，eclipse不会识别新的插件？
如果是，我尝试从我的工作区的.metadata文件夹中删除旧的jar，重新启动eclipse，但仍然存在问题。我删除了整个.metadata文件夹本身，但仍然没有帮助。
eclipse在工作空间之间共享插件/ jar。即如果同一机器上的任何其他工作区具有相同的jar？
我们使用maven作为我们的构建。 eclipse是否从本地的maven repo引用插件？
eclipse是否保持来自目标平台的数据缓存？如果是，在哪里？

这个问题实际上是让我疯狂，我需要找出一种使用最新版本的jar的方式，即版本号是一样的。 （我们对其他团队版本控制方法没有太多的控制）

任何输入都将不胜感激。

解决方案

Eclipse（p2实际上）使用ID +版本作为捆绑包的唯一标识符。这存储在缓存中，有时甚至在实例之间共享。如果您更改了jar的内容，即使稍微更改，必须更改版本号。您会注意到Eclipse使用版本号，如x.y.z.qualifier，其中限定符是时间戳（20120928-2359）。

p2的MD5只用于检查下载的有效性。

很抱歉，这是它的样子。幸运的是，Tycho和PDE / Build都可以处理.qualifier并将其更改为有意义的日期。

I have a strange problem in our Eclipse IDE (Indigo V3.7.2). We use a target platform hosted on a server which is a p2 repository built using the b3 aggregation process. We get certain components and features from a different team. Every time they deliver the plugins, the version numbers remain the same (e.g myjar_v1.0.0.jar) (of-course the size is different). We update these plugins on the remote server. After this update, the problem is that, if I use an existing workspace, I see compilation issues in my code because of the latest jar not being downloaded from the target platform. Does eclipse not recognize the new plugin because of the same version and name? If yes, I tried removing the old jar from my workspace's .metadata folder, restarted eclipse, but still the problem persists. I deleted the entire .metadata folder itself, but still it did not help. Does eclipse share the plugins/jars between workspaces. i.e. If any of other workspace on the same machine has the same jar? We use maven for our builds. Does eclipse refer to the plugin from the local maven repo? Does eclipse maintain cache of the data from the target platform? If yes, where?

This problem is actually driving me crazy and I need to find out a way to use the latest version of the jar eventhough the version number is same. (We do not have much control on the other team versioning method)

Any inputs will be greatly appreciated.

解决方案

Eclipse (well p2 actually) uses the ID + Version as the unique identifier for a bundle. This is stored in caches and sometimes even shared between instances. If you change the content of a jar, even slightly, you MUST Change the version number. You'll notice that Eclipse uses version numbers such as x.y.z.qualifier where qualifier is a timetstamp (20120928-2359).

The MD5s that p2 has are only for checking validity of the download.

I'm sorry, but this is the way it is. Luckily, both Tycho and PDE/Build can handle .qualifier and change them into a meaningful date for you.

这篇关于Eclipse不会从目标平台下载相同版本的最新jar的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！