IBM JRE Compatability与Team Explorer Everywhere插件 [英] IBM JRE Compatability with Team Explorer Everywhere Plugin
问题描述
运行IBM JRE的Eclipse使用版本为14.0.3.x的Team Explorer Everywhere插件。但是，使用相同版本的IBM JRE运行的插件的最新版本不会。
插件安装没有问题，这是在连接到VSTS时，一个例外被扔了。从com.microsoft.alm.oauth2.useragent.Version的历史简要一瞥，我确实看到TEE版本之间有变化。有人可以在这里帮助
吗？
堆栈追踪......
2017-01-17 10：39：40,217警告 [CancellableCommandThread-60 ]（com.microsoft.tfs.core.TFSConfigurationServer）获取数据提供者时出错
org.eclipse.swt.SWTException：无法执行runnable（java.lang.IllegalArgumentException：无法识别的版本字符串'pwi3270sr9fp1-20150602_01 （SR9 FP1）'。）
at org.eclipse.swt.SWT.error（Unknown Source）
at org.eclipse.swt.SWT.error（未知来源）
在组织中的
。 eclipse.ui.internal.UISynchronizer.syncExec（未知来源）
at org.eclipse.swt.widgets.Display.syncExec（未知来源）
at com.microsoft.tfs.client.common.ui.framework.help er.UIHelpers.runOnUIThread（未知来源）
at com.microsoft.tfs.client.common.ui.framework.helper。 UIHelpers.runOnUIThread（未知来源）
at com.microsoft.tfs.client.common.ui.config.UITransportRequestHandler.getCredentials（未知来源）
at com.microsoft.tfs.client.common.ui.config.UITransportRequestHandler.handleException（Unknown Source）
at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest（Unknown Source）
at ms.ws._LocationWebServiceSoap12Service.connect（Unknown Source）
at com.microsoft.tfs.core.clients.framework.location.internal.LocationWebServiceProxy.connect（Unknown Source）
at com.microsoft.tfs.core.clients.framework.location.Location Service.connect（未知来源）
at com.microsoft.tfs.core.TFSConfigurationServer.getServerDataProvider（Unknown Source）
at com.microsoft.tfs.core.TFSConnection.authenticate（Unknown Source）
at com.microsoft.tfs.client.common.ui.commands.ConnectToConfigurationServerCommand.doRun（Unknown Source）
at com.microsoft.tfs.client.common.framework.command.Command.run（Unknown Source）
at com.microsoft.tfs.client.common.framework.command.RunnableCommandAdapter.run（Unknown Source）
at at java.lang.Thread.run（Unknown Source）
引起：
$
java.lang.IllegalArgumentException：无法识别的版本字符串'pwi3270sr9fp1-20150602_01（SR9 FP1）' .com
在com.microsoft。 alm.oauth2.useragent.Version.getMatches（Unknown Source）
at com.microsoft.alm.oauth2.useragent.Version。 parseJavaRuntimeVersion（未知来源）
at com.microsoft.alm.oauth2.useragent.JavaFxProvider.checkRequirements（Unknown Source）
at com.microsoft.alm.oauth2.useragent.JavaFxProvider.checkRequirements（Unknown Source）
at com.microsoft.alm.oauth2.useragent.UserAgentImpl.scanProviders（Unknown Source）
at com.microsoft.alm.oauth2.useragent.UserAgentImpl.findCompatibleProvider（Unknown Source）
at com。 microsoft.alm.oauth2.useragent.UserAgentImpl.findCompatibleProvider（未知来源）
嗨Armon0，
我们开始解析Java runt在这个最新版本中的ime版本并没有考虑到没有遵循主要版本/次要版本/补丁的标准命名约定的SDk。我们从System.getProperty（" java.runtime.version"）
获取运行时版本，日志中的IBM版本显示为'pwi3270sr9fp1-20150602_01（SR9 FP1）'。感谢您向我们指出这一点。我将此作为一个错误记录在我们的最后。
要取消阻止，您可以使用设备流进行身份验证而不是SWT。要执行此操作，请转到您的eclipse.ini文件，对于我而言，C：\ Users \< user> \ eclipse \ java-neon \ eclipse \ eclipse.ini但它取决于您安装Eclipse的位置。将此行添加
到文件的底部： -DuserAgentProvider = none
重新启动Eclipse，然后再次尝试登录。它将使您通过浏览器使用提供的代码登录。如果有帮助请告诉我。
非常感谢和抱歉给您带来不便，
-Leah
Eclipse running the IBM JRE worked with the Team Explorer Everywhere plugin at version of 14.0.3.x . However, the latest version of the plugin running with the very same version of the IBM JRE does not.
The plugin installs without issue, it is that when doing a connect to VSTS, an exception is thrown. From a brief glance of history on com.microsoft.alm.oauth2.useragent.Version, I do see that there were changes between the versions of TEE. Can someone assist here?
Stack trace...
2017-01-17 10:39:40,217 WARN [CancellableCommandThread-60] (com.microsoft.tfs.core.TFSConfigurationServer) Error getting data providerorg.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Unrecognized version string 'pwi3270sr9fp1-20150602_01 (SR9 FP1)'.)
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Unknown Source)
at org.eclipse.ui.internal.UISynchronizer.syncExec(Unknown Source)
at org.eclipse.swt.widgets.Display.syncExec(Unknown Source)
at com.microsoft.tfs.client.common.ui.framework.helper.UIHelpers.runOnUIThread(Unknown Source)
at com.microsoft.tfs.client.common.ui.framework.helper.UIHelpers.runOnUIThread(Unknown Source)
at com.microsoft.tfs.client.common.ui.config.UITransportRequestHandler.getCredentials(Unknown Source)
at com.microsoft.tfs.client.common.ui.config.UITransportRequestHandler.handleException(Unknown Source)
at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(Unknown Source)
at ms.ws._LocationWebServiceSoap12Service.connect(Unknown Source)
at com.microsoft.tfs.core.clients.framework.location.internal.LocationWebServiceProxy.connect(Unknown Source)
at com.microsoft.tfs.core.clients.framework.location.LocationService.connect(Unknown Source)
at com.microsoft.tfs.core.TFSConfigurationServer.getServerDataProvider(Unknown Source)
at com.microsoft.tfs.core.TFSConnection.authenticate(Unknown Source)
at com.microsoft.tfs.client.common.ui.commands.ConnectToConfigurationServerCommand.doRun(Unknown Source)
at com.microsoft.tfs.client.common.framework.command.Command.run(Unknown Source)
at com.microsoft.tfs.client.common.framework.command.RunnableCommandAdapter.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by:
java.lang.IllegalArgumentException: Unrecognized version string 'pwi3270sr9fp1-20150602_01 (SR9 FP1)'.
at com.microsoft.alm.oauth2.useragent.Version.getMatches(Unknown Source)
at com.microsoft.alm.oauth2.useragent.Version.parseJavaRuntimeVersion(Unknown Source)
at com.microsoft.alm.oauth2.useragent.JavaFxProvider.checkRequirements(Unknown Source)
at com.microsoft.alm.oauth2.useragent.JavaFxProvider.checkRequirements(Unknown Source)
at com.microsoft.alm.oauth2.useragent.UserAgentImpl.scanProviders(Unknown Source)
at com.microsoft.alm.oauth2.useragent.UserAgentImpl.findCompatibleProvider(Unknown Source)
at com.microsoft.alm.oauth2.useragent.UserAgentImpl.findCompatibleProvider(Unknown Source)
Hi Armon0,
We started to parse for the Java runtime version in this latest release and did not account for SDk that didn't follow the standard naming convention of major version/minor version/patch. We get the runtime version from System.getProperty("java.runtime.version") and the IBM version from the log shows as 'pwi3270sr9fp1-20150602_01 (SR9 FP1)'. Thank you for pointing this out to us. I will log this as a bug on our end.
To unblock you though, you can use device flow for authentication instead of SWT. To do this go to your eclipse.ini file which for me is here C:\Users\<user>\eclipse\java-neon\eclipse\eclipse.ini but it depends where you installed Eclipse. Add this line to the bottom of the file: -DuserAgentProvider=none
Restart Eclipse and then try to log in again. It will make you log in through the browser with a provided code. Let me know if this helps.
Thanks and sorry for the inconvenience,
-Leah
这篇关于IBM JRE Compatability与Team Explorer Everywhere插件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
