[jbosstools-issues] [JBoss JIRA] (JBIDE-22951) HIDDEN below ExternalProcessLauncher.launch (thrown in DOMParser.parse)
Jeff MAURY (JIRA)
issues at jboss.org
Wed Apr 18 12:13:30 EDT 2018
[ https://issues.jboss.org/browse/JBIDE-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff MAURY updated JBIDE-22951:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> HIDDEN below ExternalProcessLauncher.launch (thrown in DOMParser.parse)
> -----------------------------------------------------------------------
>
> Key: JBIDE-22951
> URL: https://issues.jboss.org/browse/JBIDE-22951
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to restore classpath entry.
> {noformat}
> HIDDEN: FWK005 parse may not be called while parsing.
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(null:-1)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(null:-1)
> at org.eclipse.jdt.launching.JavaRuntime.newRuntimeClasspathEntry(JavaRuntime.java:724)
> at org.eclipse.jdt.launching.StandardClasspathProvider.recoverRuntimePath(StandardClasspathProvider.java:102)
> at org.eclipse.jdt.launching.StandardClasspathProvider.computeUnresolvedClasspath(StandardClasspathProvider.java:66)
> at org.eclipse.jdt.launching.JavaRuntime.computeUnresolvedRuntimeClasspath(JavaRuntime.java:1246)
> at org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getBootpathExt(AbstractJavaLaunchConfigurationDelegate.java:296)
> at org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getVMSpecificAttributesMap(AbstractJavaLaunchConfigurationDelegate.java:563)
> at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:69)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launch(ExternalProcessLauncher.java:250)
> at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launchAsExternalProcess(ExternalProcessLauncher.java:81)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:177)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:129)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:25)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.debug.core | 3.10.0.v20150303-1130 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.200.v20160518-1858 |
> | org.eclipse.jdt.launching | 3.8.0.v20150527-0946 | 3.8.100.v20160505-0636 |
> | org.jboss.tools.browsersim.eclipse | 3.7.1.Final-v20160331-0511-B89 | 3.8.0.Final-v20160609-2253-B3 |
> | org.jboss.tools.cordovasim.eclipse | 3.7.1.Final-v20160331-0435-B86 | 3.8.0.Final-v20160609-2302-B3 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572f2d5be4b0a54983279461] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbosstools-issues
mailing list