[JBoss JIRA] (JBIDE-17485) CordovaSim InAppBrowser does not return the correct url on loadstart event
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17485?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-17485:
-------------------------------------
[~gercan], I'm not able to run project on device - JBIDE-17498. Any ideas?
> CordovaSim InAppBrowser does not return the correct url on loadstart event
> --------------------------------------------------------------------------
>
> Key: JBIDE-17485
> URL: https://issues.jboss.org/browse/JBIDE-17485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.2.0.Beta1
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
> Attachments: index.html
>
>
> In the loadstart event we ask for the url event.url. In the iOS simulator it returns the url of the page currently displayed in the inapp browser. However, in the CordovaSim the url will always return the url of the first page opened in the inapp browser not the one of the currently displayed one.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17298) NPE when opening preview tab
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17298?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17298.
-------------------------------
Verified with JBDS Beta2-v20140601-0744-B106
> NPE when opening preview tab
> ----------------------------
>
> Key: JBIDE-17298
> URL: https://issues.jboss.org/browse/JBIDE-17298
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
>
> A:
> 1. Open any HTML page with JBoss Tools HTML Editor
> 2. Open Preview tab
> 3. Restart Eclipse
> *Eclipse fails to start*
> or
> B:
> 1. Open any HTML page with JBoss Tools HTML Editor
> 2. Open Source tab
> 3. Restart Eclipse
> 4. Click on Preview tab:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart.getPreviewWebBrowser(VpvEditorPart.java:903)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:316)
> at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:294)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1182)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3110)
> at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1794)
> at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:283)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3416)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17449) VPE toolbar has many disabled toolitems when HTML page is opened
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17449?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17449:
------------------------------------------------
Toolbar was made using xulrunner tools so it cannot be implemented right now. This is good feature, it must be, but it was not implemented because of lack of time. Will be implemented for jbds9.
> VPE toolbar has many disabled toolitems when HTML page is opened
> ----------------------------------------------------------------
>
> Key: JBIDE-17449
> URL: https://issues.jboss.org/browse/JBIDE-17449
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta3
>
>
> 1. Open HTML page in VPE editor with Visual/Source tab opened
> ERROR: Many Toolitems of VPE toolbar are disabled
> !vpetoolbardisabled.png!
> ERROR: Formatting toolbar is missng
> For JSP page it works as expected
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-16952) Greater-than sign incorrectly considered an invalid character in HTML5 text
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16952?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16952.
-------------------------------
Verified with JBDS Beta2-v20140601-0744-B106
> Greater-than sign incorrectly considered an invalid character in HTML5 text
> ---------------------------------------------------------------------------
>
> Key: JBIDE-16952
> URL: https://issues.jboss.org/browse/JBIDE-16952
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Environment: JBoss Tools version that is in JBDS 7.1.1.GA
> Reporter: Ron Šmeral
> Assignee: Victor Rubezhny
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
>
> A HTML5 file like the following
> {code:html}
> <!DOCTYPE html>
> <html>
> <head><title>README</title></head>
> <body>
> <p>To run the tests, select Run As –> JUnit Test in the context menu.</p>
> </body>
> </html>
> {code}
> results in a warning of type _HTML Problem_ with the text _Invalid character used in text string_, marking the greater-than sign (">").
> This warning is incorrect, since ">" is a valid character in HTML5 text elements as confirmed by the W3C validator.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17418) Browsing for entities dialog shouldn't be empty by default in new JAX-RS Resource wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17418?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-17418:
-------------------------------------
about **, if the user removes it, will he see classes from other source folders (imagine using stuff in a target/generated-sources/ folder)?
> Browsing for entities dialog shouldn't be empty by default in new JAX-RS Resource wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-17418
> URL: https://issues.jboss.org/browse/JBIDE-17418
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
> Attachments: JBIDE-17418.png
>
>
> When a project contains JPA entities and you try to create a new JAX-RS Resource, browsing for "Target Entity" displays a blank viewer by default. I expected all entities from the project to be displayed, similar to how other wizards work.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Ilya Buziuk (JIRA)
Ilya Buziuk created JBIDE-17498:
-----------------------------------
Summary: Can't run default hybrid project on device
Key: JBIDE-17498
URL: https://issues.jboss.org/browse/JBIDE-17498
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.2.0.Beta1
Environment: windows
Reporter: Ilya Buziuk
After choosing *Run As.. -> Run on Android Device* getting exception:
{code}
!ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618
!MESSAGE Ant Build Failed
!STACK 1
org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
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:54)
Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
at org.apache.tools.ant.Task.perform(Task.java:347)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
... 12 more
!SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618
!MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
!STACK 0
E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
at org.apache.tools.ant.Task.perform(Task.java:347)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
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:54)
!ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620
!MESSAGE Build failed... Build artifact does not exist
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17449) VPE toolbar has many disabled toolitems when HTML page is opened
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17449?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17449:
-------------------------------------
What is the reason to not implement Formatting toolbar when file is opened with new Preview editor especially when toolbar is available for xhtml and jsp pages. It's pretty much inconsistent. This toolbar is used for editing not for preview and i think should be available for HTML pages also.
> VPE toolbar has many disabled toolitems when HTML page is opened
> ----------------------------------------------------------------
>
> Key: JBIDE-17449
> URL: https://issues.jboss.org/browse/JBIDE-17449
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta3
>
>
> 1. Open HTML page in VPE editor with Visual/Source tab opened
> ERROR: Many Toolitems of VPE toolbar are disabled
> !vpetoolbardisabled.png!
> ERROR: Formatting toolbar is missng
> For JSP page it works as expected
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17418) Browsing for entities dialog shouldn't be empty by default in new JAX-RS Resource wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17418?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-17418:
-------------------------------------
Well, entity means it's persistence related, but that could very well be pure hibernate (or other) entities, not JPA.
I like being able to see the JPA entities first, but could we easily add a kind of separator and display other classes below?
> Browsing for entities dialog shouldn't be empty by default in new JAX-RS Resource wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-17418
> URL: https://issues.jboss.org/browse/JBIDE-17418
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
> Attachments: JBIDE-17418.png
>
>
> When a project contains JPA entities and you try to create a new JAX-RS Resource, browsing for "Target Entity" displays a blank viewer by default. I expected all entities from the project to be displayed, similar to how other wizards work.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17449) VPE toolbar has many disabled toolitems when HTML page is opened
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17449?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-17449 at 6/2/14 6:02 AM:
-------------------------------------------------------------
What is the reason to not implement Formatting toolbar when file is opened with new Preview editor especially when toolbar is available for xhtml and jsp pages? It's pretty much inconsistent. This toolbar is used for editing not for preview and i think should be available for HTML pages also.
was (Author: vpakan):
What is the reason to not implement Formatting toolbar when file is opened with new Preview editor especially when toolbar is available for xhtml and jsp pages. It's pretty much inconsistent. This toolbar is used for editing not for preview and i think should be available for HTML pages also.
> VPE toolbar has many disabled toolitems when HTML page is opened
> ----------------------------------------------------------------
>
> Key: JBIDE-17449
> URL: https://issues.jboss.org/browse/JBIDE-17449
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta3
>
>
> 1. Open HTML page in VPE editor with Visual/Source tab opened
> ERROR: Many Toolitems of VPE toolbar are disabled
> !vpetoolbardisabled.png!
> ERROR: Formatting toolbar is missng
> For JSP page it works as expected
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months