Exception "com/ibm/icu/util/StringTokenizer" when opening XML file with XML Editor after installing Subclipse

[Faliorn]

Hi, my name is Alex, and I have been working with Eclipse / Subclipse for more than 10 years now :)

I have downloaded Eclipse 2022-09 and, after installing Subclipse from https://subclipse.github.io/updates/, I receive an error regarding "com/ibm/icu/util/StringTokenizer" instead of java.util.StringTokenizer when I open an XML file with XML Editor.

I've narrowed it down to the installation of the Subclipse/Subclipse part of the installation. CoreSVN Kit, JNA etc install just fine.

Also, uninstalling Subclipse doesn't fix the problem. I need to restart with a clean eclipse configuration to make it work again.

I think it has to do with the configuration/org.eclipse.osgi folder. There are a number of files changed by the installation on com/ibm/icu/impl folder.

Thanks for your efforts, great software. Kind regards.

Alex.

[markphip]

Hi Alex, unfortunately no one really works on this code any more. If you figure something out and want to submit a PR I will try to review and merge it.

Not sure what is happening, as you can see we do not use that class anywhere: https://github.com/search?q=repo%3Asubclipse%2Fsubclipse%20StringTokenizer&type=code

I do not doubt what you are seeing, I am just not certain what would be causing it. Maybe it is some kind of transitive dependency. I recall there was always an error opening XML files in a the Remote Repository viewer but that was because the XML Editor did not implement the JFace interface that is standard for Eclipse. Regardless, it does not seem to be what you are reporting here anyway.

[Faliorn]

Investigating a bit more, I managed to make it work by copying configuration/org.eclipse.equinox.simpleconfigurator/bundles.info from a working copy to a non-working one.

The working file has this line:

• com.ibm.icu,67.1.0.v20200706-1749,plugins/com.ibm.icu_67.1.0.v20200706-1749.jar,4,false

The non-working file has these lines:

• com.collabnet.subversion.merge,4.2.0.1,plugins/com.collabnet.subversion.merge_4.2.0.1.jar,4,false
• com.ibm.icu.base,58.2.0.v20170418-1837,plugins/com.ibm.icu.base_58.2.0.v20170418-1837.jar,4,false
• org.tigris.subversion.clientadapter,1.10.0,plugins/org.tigris.subversion.clientadapter_1.10.0.jar,4,false
• org.tigris.subversion.subclipse.core,4.3.3.202012181204,plugins/org.tigris.subversion.subclipse.core_4.3.3.202012181204.jar,4,false
• org.tigris.subversion.subclipse.ui,4.3.3.202012181204,plugins/org.tigris.subversion.subclipse.ui_4.3.3.202012181204.jar,4,false

NOTE: After testing, the com.ibm.icu line is the only one that matters for the case.

Hope it helps. I'm sorry to hear that, because the alternative to use SVN has serious performance issues, at least in my case where we have thousands of files.

Thanks Mark and best regards

[markphip]

Looking at what we require when you install nothing jumps out at me:

https://github.com/subclipse/subclipse/blob/master/features/feature.subclipse/feature.xml

All I can think of would be if one of these Eclipse plugins we require has been retired and our install is causing Eclipse to pull in an old plugin that then pulls in an old version of the ICU plugin. I do believe there are eclipse.org plugins that use and require that plugin so I guess this is possible. If this is the problem then we might be able to drop the requirement, make it optional or update it to whatever has replaced it.

I cannot think of any easy way to figure out what might have caused it though. Perhaps something in the installation log has details of the changes made to your configuration when you do the install that might point at something.

It has to be some kind of a transitive dependency problem though.

[C4J]

I get this error when I use the Eclipse option to validate a project.

The sequence of events for me to reproduce this error are to

1. Fix an update error which seems to be normal these days with updates 👎
   No repository found at http://download.eclipse.org/technology/m2e/releases.
   Change to https://download.eclipse.org/technology/m2e/releases/latest

2. Install a Apache Tomcat Web Server.

Then validate some projects. Most but not all come back with the error stated in this post.