[JBoss JIRA] (JBIDE-23634) cordovasim: Invalid character '\u0187' inFileWriter.js
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23634?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23634:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> cordovasim: Invalid character '\u0187' inFileWriter.js
> ------------------------------------------------------
>
> Key: JBIDE-23634
> URL: https://issues.jboss.org/browse/JBIDE-23634
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.4.2.Final
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> Created from the forum question - https://developer.jboss.org/message/965770?et=watches.email.thread#965770
> {quote}
> I'm trying to run our hybrid app on the cordova sim but I'm getting the following error:
>
> !JavaScript ERROR: SyntaxError: Invalid character '\u0187' on line 2 for http://localhost:54938/plugins/cordova-plugin-file/www/FileWriter.js
> !JavaScript ERROR: Error: Module cordova-plugin-file.FileWriter does not exist. on line 1469 for http://localhost:54938/cordova.js
> !JavaScript LOG: deviceready has not fired after 5 seconds.
> !JavaScript LOG: Channel not fired: onPluginsReady
> !JavaScript LOG: Channel not fired: onCordovaReady
>
> I'm sure there is nothing wrong with the app because we can build it just fine using ionic build. I've Googled the error and they said that it is a bug on version 8. But I am now using version 10 of JBoss Developer. Does anyone knows how to fix this? Below is my environment:
>
> Thanks
>
> JBoss Developer Studio 10.1.0
> Eclipse Neon 1
> Cordova CLI: 6.4.0
> Ionic CLI Version: 2.1.12
> Ionic App Lib Version: 2.1.7
> ios-deploy version: Not installed
> ios-sim version: Not installed
> OS: Windows 7
> Node Version: v6.9.1
> Xcode version: Not installed
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-24307) Filter out Build config which have no git url configured in "Import OpenShift Application" dialog
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24307?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24307:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Filter out Build config which have no git url configured in "Import OpenShift Application" dialog
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24307
> URL: https://issues.jboss.org/browse/JBIDE-24307
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Labels: import_wizard, openshift_v3
> Fix For: 4.6.x
>
> Attachments: image-2017-04-25-15-22-03-598.png, image-2017-04-25-15-22-12-510.png
>
>
> it will avoid to have an error dialog just after
> !image-2017-04-25-15-22-12-510.png|thumbnail!
> Even more that thsi information is already retrieved to be displayed in "Build config details"
> !image-2017-04-25-15-22-03-598.png|thumbnail!
> Anothe rpossibility is to greyet out them with a tooltip explaining why we can't select them
> and/or disabled Next:Finish buttons
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25557) OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25557?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25557:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25557
> URL: https://issues.jboss.org/browse/JBIDE-25557
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.5.2.AM3
> Environment: FC27 + OpenJDK9
> Red Hat JBoss Developer Studio Version: 11.2.0.AM3
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.6.x
>
>
> Forge does not start:
> {code:java}
> null
> org.eclipse.core.jobs
> Error
> Thu Jan 11 12:59:40 CET 2018
> An internal error occurred during: "Starting JBoss Forge 3.7.2.Final".
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.projects.ProjectFactory] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.util.ForgeHelper.initializeFurnaceRuntime(ForgeHelper.java:99)
> at org.jboss.tools.forge.ui.util.ForgeHelper.access$0(ForgeHelper.java:89)
> at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:57)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {code:java}
> null
> org.eclipse.ui
> Error
> Thu Jan 11 12:59:40 CET 2018
> Unhandled event loop exception
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.shell.spi.ShellHandle] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.internal.cli.AeshConsole.start(AeshConsole.java:46)
> at org.jboss.tools.aesh.ui.view.AbstractTextViewer$1.run(AbstractTextViewer.java:46)
> at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
> at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21822:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Fix For: 4.6.x
>
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22951) HIDDEN below ExternalProcessLauncher.launch (thrown in DOMParser.parse)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22951?page=com.atlassian.jira.plugi... ]
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/572f2d5be4b0a54983...] 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)
7 years, 11 months
[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24960:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> JBDS 11 produces warnings about missing schemas inconsistently
> --------------------------------------------------------------
>
> Key: JBIDE-24960
> URL: https://issues.jboss.org/browse/JBIDE-24960
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.5.0.Final
> Reporter: Michal Jurc
> Assignee: Rob Stryker
> Fix For: 4.6.x
>
>
> The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart:
> ||Description||Resource||Path||Location||Type||
> |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem|
> The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it.
> This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months