Community
Participate
Working Groups
Build Identifier: 20100617-1415 There are three jar files that appear to be duplicated in the RCP release of Helios. org.apache.commons.httpclient_3.1.0.v201005080502.jar org.apache.commons.httpclient_3.1.0.v20080605-1935.jar org.apache.commons.codec_1.3.0.v20100106-1700.jar org.apache.commons.codec_1.3.0.v20100518-1140.jar org.apache.commons.logging_1.0.4.v200904062259.jar org.apache.commons.logging_1.0.4.v201005080501.jar Having these duplicate jars cause inconsistent behavior. For instance, a plugin can work fine when launched internally (spawn a second instance of Eclipse). Conversely, when the plugin installed from an update site into Eclipse and then run it can fail. The workaround is to delete the duplicate jars and then the plugin works as normal, but I am not sure what else would break as a result. Discussion thread about this issue: http://www.eclipse.org/forums/index.php?t=msg&th=173778&start=0&S=43442c6c7c5542427f4232be4e189aed Reproducible: Always Steps to Reproduce: Simply unzip eclipse-rcp-helios-win32.zip and look in the plugins directory.
Can you explain in more detail the steps that cause you problems? I'm downloading the win32 helios rcp zip now. There probably should not be two copies of the plug-ins included, most likely two features are marked as requiring different versions. That being said, it shouldn't break things to have two versions of non-singleton bundles available.
I can confirm that the RCP Eclipse download contains the duplicate bundles. So there may be a problem with how that download is being packaged. I still would like to understand what exact problems it is causing as we should be avoiding them in PDE.
Specifically it would appear that Eclipse is seeing two jar files and picking the wrong jar file with which to obtain a needed class. My PropfindMethod extends a class found in both httpclient jars, the difference is that the older version of the class has a different method footprint than the same class in the newer jar. When Eclipse runs my plugin it tries to use that newer class and this stacktrace occurs: java.lang.IncompatibleClassChangeError: Class com.mycompany.vfs.utils.PropfindMethod does not implement the requested interface org.apache.commons.httpclient.HttpMethod at org.apache.commons.httpclient.HttpClient.executeMethod(HttpC lient.java:383) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpC lient.java:323) ... I tried to go into the plugin.xml=>dependences and change the version on org.apache.commons.httpclient. That didn't work as it appears that the version entry screen only accepts versions in the format of n.n.n, and not n.n.n.v200904062259. Since both jars have the same n.n.n version number this wasn't a viable solution.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
