February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19197) jst/jsf New and Noteworthy for 4.3.0.Alpha1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19197?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19197: -------------------------------------- Assignee: Alexey Kazakov > jst/jsf New and Noteworthy for 4.3.0.Alpha1 > ------------------------------------------- > > Key: JBIDE-19197 > URL: https://issues.jboss.org/browse/JBIDE-19197 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19200) Core/General New and Noteworthy for 4.3.0.Alpha1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19200?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19200: -------------------------------------- Assignee: Alexey Kazakov > Core/General New and Noteworthy for 4.3.0.Alpha1 > ------------------------------------------------ > > Key: JBIDE-19200 > URL: https://issues.jboss.org/browse/JBIDE-19200 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Core/General is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Core/General by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18244) org.eclipse.core.runtime.AssertionFailedException when editing ftl file

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18244?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-18244: --------------------------------------- I just wanted to add that the plugin is next to useless because of this (and a few more glitches), it show these assertion error popups(!) so often. And when it starts doing that, often it will pop it up after each single key stroke, so you have to close the editor, and reopen it. > org.eclipse.core.runtime.AssertionFailedException when editing ftl file > ----------------------------------------------------------------------- > > Key: JBIDE-18244 > URL: https://issues.jboss.org/browse/JBIDE-18244 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Alpha1 > > Attachments: assertion-exception.ogv > > > When editing ftl file I received assertion failed exception. See the screencast. What I did was to adding new line and then remove it by back key. Before it I was using code completion (might be related) > {code} > org.eclipse.core.runtime.AssertionFailedException: assertion failed: > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) > at org.eclipse.jface.text.Position.setLength(Position.java:185) > at org.eclipse.jface.text.rules.FastPartitioner.computePartitioning(FastPartitioner.java:634) > at org.eclipse.jface.text.AbstractDocument.computePartitioning(AbstractDocument.java:1430) > at org.eclipse.jface.text.TextUtilities.computePartitioning(TextUtilities.java:431) > at org.eclipse.jface.text.presentation.PresentationReconciler.createPresentation(PresentationReconciler.java:451) > at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:569) > at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:567) > at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.textChanged(PresentationReconciler.java:227) > at org.eclipse.jface.text.TextViewer.updateTextListeners(TextViewer.java:2830) > at org.eclipse.jface.text.TextViewer$VisibleDocumentListener.documentChanged(TextViewer.java:403) > at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged2(AbstractDocument.java:769) > at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:736) > at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:721) > at org.eclipse.jface.text.AbstractDocument.fireDocumentChanged(AbstractDocument.java:796) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1191) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) > at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248) > at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7268) > at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8111) > at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2285) > at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7058) > at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5959) > at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5986) > at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5663) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > 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.sendKeyEvent(Widget.java:1424) > at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824) > at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3269) > at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:777) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > 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.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.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19096: ------------------------------------- Attachment: existing-v2-connection.png > Connection wizard: Allow v2 and v3 Connections > ---------------------------------------------- > > Key: JBIDE-19096 > URL: https://issues.jboss.org/browse/JBIDE-19096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: existing-v2-connection.png, fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png > > > !screenshot-openshift-signin.png! > In order to allow us to present v2 and v3 connections we have to change the connection wizard: > When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: > * v2 connections currently use username/password (and will most likely also allow x509, kerberos) > * v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19096: ------------------------------------- Description: the existing UI for v2 OpenShift: * new connection: !screenshot-openshift-signin.png! * existing connection: !existing-v2-connection.png! In order to allow us to present v2 and v3 connections we have to change the connection wizard: When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: * v2 connections currently use username/password (and will most likely also allow x509, kerberos) * v3 connections will most likely require OAuth settings. was: !screenshot-openshift-signin.png! In order to allow us to present v2 and v3 connections we have to change the connection wizard: When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: * v2 connections currently use username/password (and will most likely also allow x509, kerberos) * v3 connections will most likely require OAuth settings. > Connection wizard: Allow v2 and v3 Connections > ---------------------------------------------- > > Key: JBIDE-19096 > URL: https://issues.jboss.org/browse/JBIDE-19096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: existing-v2-connection.png, fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png > > > the existing UI for v2 OpenShift: > * new connection: > !screenshot-openshift-signin.png! > * existing connection: > !existing-v2-connection.png! > In order to allow us to present v2 and v3 connections we have to change the connection wizard: > When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: > * v2 connections currently use username/password (and will most likely also allow x509, kerberos) > * v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18177: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-vpe/pull/295, https://github.com/jbosstools/jbosstools-jst/pull/442 (was: https://github.com/jbosstools/jbosstools-vpe/pull/295) > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, new_and_noteworthy, requirements > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19177) Add Openshift v3 property panels for various resources

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19177?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19177: ------------------------------------- Assignee: Jeff Cantrill > Add Openshift v3 property panels for various resources > ------------------------------------------------------ > > Key: JBIDE-19177 > URL: https://issues.jboss.org/browse/JBIDE-19177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Add Property panels for the various resource types so that when you click on a IResource it displays significant properties of that resource -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19000) As a user I want to browse the resources for my projects

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19000?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19000: --------------------------------------- [~adietish] Shouldnt we leave this open until the other issues are resolved....and mark it as resolved so QA can test it? > As a user I want to browse the resources for my projects > -------------------------------------------------------- > > Key: JBIDE-19000 > URL: https://issues.jboss.org/browse/JBIDE-19000 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Alpha1 > > Attachments: 2015-01-06 22.13.bmml, 2015-01-06 22.13.bmml, 2015-01-06 22.13.png, OpenShift console.pdf > > > * Raw view of OpenShift project resources (e.g. services, pods, build configs). > * Resources will display the relevant labels and selectors to allow a user to infer associations between resources -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19179) Add deferred loading and error handling to the openshift v3 explorer

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19179?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19179: --------------------------------------- [~adietish] Added deferred loading and refresh of the connection > Add deferred loading and error handling to the openshift v3 explorer > -------------------------------------------------------------------- > > Key: JBIDE-19179 > URL: https://issues.jboss.org/browse/JBIDE-19179 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Add deferred loading and error handling similiar to v2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19187) CordovaSim + localhost:8080 fail

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19187?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-19187: ------------------------------------- on the cross domain...when did this change? I do not remember ever having to make this change and have run the code seen in this jira at least a dozen times in demos. http://screencast.com/t/6ANJRgkg8VK > CordovaSim + localhost:8080 fail > -------------------------------- > > Key: JBIDE-19187 > URL: https://issues.jboss.org/browse/JBIDE-19187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.Final > Environment: JBDS 8 > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > Attachments: hybrid4001.zip, localhost_error.png > > > The following logic used to work and now fails: > $.getJSON("http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members", function(data) { > $("#contacts").empty(); > var items = []; > $.each(data, function(key, val) { > console.log("item: " + key + " " + val.name); > items.push("<li><a href='#"+ key + "'>" + val.name +"</a></li>"); > }); > $("#contacts").append(items); > $("#contacts").listview("refresh"); > }); > ------- > as seen in this youtube video and comments > https://www.youtube.com/watch?v=FstGLMr3W8s&feature=gp-n-y&google_comment... > ---- Using the Chrome Debugger (via CordovaSim, right-click, Dev Tools) > has the following error message: > https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo... 500 () rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=h... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2015