Support for IBM EWM 7.0.2 Eclipse Client in Eclipse versions 4.17 and beyond? (Java-11 based Eclipse)

 Good day!

I'm trying to get information on IBM's plans with EWM (formerly RTC) to support versions of their client for more recent Eclipse after 4.11.  Eclipse 4.11 is also known as Eclipse 2019-03.

We are running EWM 7.0.2, and need to upgrade a Java 11-based Eclipse, either:

  Eclipse 4.21 (2021-09)  -- desired

  Eclipse 4.17 (2020-09)  -- minimum acceptable

Regarding EWM, I looked into IBM's docs for 7.0.2, following their "System Requirements" page for IBM EWM 7.0.2, then tab " Eclipse Runtime Environment", where Eclipse Version "4.11 and future fix packs" are listed.

However the Details View from

here:

https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/prereqTabViewDetails?osPlatform=spcrAllValues&dsrType=tsr&deliverableId=BD41C8E05A1C11E982882C5D069DA07A&productName=IBM+Engineering+Lifecycle+Management+Base+7.0&prereqId=4882C3E0C4BA11E7AD0EC24C9513D95F&prereqName=Eclipse+4.11&capName=Eclipse+Runtime+Environment&isDUOnly=false&isMandatory=true&osPlatforms=Windows&duComponentIds=D004%7CD002%7CD001%7CD003%7CS005%7CS006

has notes about Eclipse Runtime Environment which says "Only Java 8 is supported". 

===

Does anyone know anything about when a "p2 Install Repository" to provide the "IBM Engineering Workflow Management Client Feature" plugin will be available to install and run in a Java 11-based Eclipse?

Perhaps some kind of fix pack of an updated p2 repo zip file?

===

 WHAT I TRIED:

I did give a try to use the 7.0.2 p2Repo with Eclipse 4.17 (2020-09).  I first set up an 11.0.9 JDK on Windows:

C:\Program Files\Java\jdk-11.0.9\bin>java -version

java version "11.0.9" 2020-10-20 LTS

Java(TM) SE Runtime Environment 18.9 (build 11.0.9+7-LTS)

Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.9+7-LTS, mixed mode)

Then configured Eclipse 4.17 (2020-09) with the above as the "-vm" argument, installed EWM-Client-p2Repo-7.0.2.zip, and restarted.

I can get the UI to appear to create a Teams repository connection, but after entering correct credentials to set up a repository connection, an error dialog appears with this message:

An internal error occurred during: "Searching for root folder content...".

Could not get value of field private transient sun.util.calendar.BaseCalendar$Date java.util.Date.cdate in 2020-11-10 15:47:53.722

Similarly, in the .metadata/.log file there is this trace when trying to set up the connection:

!ENTRY org.eclipse.core.jobs 4 2 2022-02-25 15:27:35.079

!MESSAGE An internal error occurred during: "Applying Repository Connection Changes".

!STACK 0

java.lang.RuntimeException: Could not get value of field private transient sun.util.calendar.BaseCalendar$Date java.util.Date.cdate in 2019-05-23 21:50:16.106

        at com.ibm.team.repository.common.internal.util.ObjectSizer.getFieldValue(ObjectSizer.java:427)

        at com.ibm.team.repository.common.internal.util.ObjectSizer.getDeepSize(ObjectSizer.java:333)

        at com.ibm.team.repository.common.model.impl.ItemHandleImpl.size(ItemHandleImpl.java:554)

        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)

        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.base/java.lang.reflect.Method.invoke(Method.java:567)

        at com.ibm.team.repository.common.internal.util.ItemStore$ItemInvocationHandler.invoke(ItemStore.java:597)

        at jdk.proxy12/jdk.proxy12.$Proxy36.size(Unknown Source)

        at com.ibm.team.repository.common.internal.util.ItemStore.getSize(ItemStore.java:478)

        at com.ibm.team.repository.common.internal.util.ItemStore.access$2(ItemStore.java:476)

        at com.ibm.team.repository.common.internal.util.ItemStore$WeakItemDescriptor.<init>(ItemStore.java:495)

        at com.ibm.team.repository.common.internal.util.ItemStore.putItem(ItemStore.java:160)

        at com.ibm.team.repository.common.internal.util.ItemStore.putItems(ItemStore.java:231)

        at com.ibm.team.repository.client.internal.ItemManager.applyNewStates(ItemManager.java:1452)

        at com.ibm.team.repository.client.internal.ItemManager.applyItemUpdates(ItemManager.java:732)

        at com.ibm.team.repository.client.internal.ItemManager.applyItemUpdates(ItemManager.java:722)

        at com.ibm.team.repository.client.internal.TeamRepository.internalLogin(TeamRepository.java:1618)

        at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:673)

        at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:646)

        at com.ibm.team.process.internal.rcp.ui.RepositoryPropertyPage.resetConnection(RepositoryPropertyPage.java:224)

        at com.ibm.team.process.internal.rcp.ui.RepositoryPropertyPage.save(RepositoryPropertyPage.java:105)

        at com.ibm.team.process.internal.rcp.ui.RepositoryPropertyPage.access$0(RepositoryPropertyPage.java:102)

        at com.ibm.team.process.internal.rcp.ui.RepositoryPropertyPage$1.run(RepositoryPropertyPage.java:89)

        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field private transient sun.util.calendar.BaseCalendar$Date java.util.Date.cdate accessible: module java.base does not "opens java.util" to unnamed module @1d7201cb

        at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357)

        at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)

        at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:177)

        at java.base/java.lang.reflect.Field.setAccessible(Field.java:171)

        at com.ibm.team.repository.common.internal.util.ObjectSizer.getFieldValue(ObjectSizer.java:424)

        ... 24 more

Clearly it didn't  work.

ANY INFORMATION ON FUTURE AVAILABILITY WOULD BE HIGHLY APPRECIATED! 

Or, information that EWM updates are no longer going to be produced; that would also help us to start looking into alternatives.

Thanks!