January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19104) Move org.jboss.tools.forge.runtime.ext to org.jboss.tools.forge.ext.feature

by Koen Aers (JIRA)

Koen Aers created JBIDE-19104: --------------------------------- Summary: Move org.jboss.tools.forge.runtime.ext to org.jboss.tools.forge.ext.feature Key: JBIDE-19104 URL: https://issues.jboss.org/browse/JBIDE-19104 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19104) Move org.jboss.tools.forge.runtime.ext to org.jboss.tools.forge.ext.feature

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19104?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-19104: --------------------------------- Assignee: Koen Aers > Move org.jboss.tools.forge.runtime.ext to org.jboss.tools.forge.ext.feature > --------------------------------------------------------------------------- > > Key: JBIDE-19104 > URL: https://issues.jboss.org/browse/JBIDE-19104 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19103) Remove all functionality from org.boss.tools.forge.runtime.ext

by Koen Aers (JIRA)

Koen Aers created JBIDE-19103: --------------------------------- Summary: Remove all functionality from org.boss.tools.forge.runtime.ext Key: JBIDE-19103 URL: https://issues.jboss.org/browse/JBIDE-19103 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19103) Remove all functionality from org.boss.tools.forge.runtime.ext

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19103?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-19103: --------------------------------- Assignee: Koen Aers > Remove all functionality from org.boss.tools.forge.runtime.ext > -------------------------------------------------------------- > > Key: JBIDE-19103 > URL: https://issues.jboss.org/browse/JBIDE-19103 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19102) Remove org.jboss.tools.forge.runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19102?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-19102: --------------------------------- Assignee: Koen Aers > Remove org.jboss.tools.forge.runtime > ------------------------------------- > > Key: JBIDE-19102 > URL: https://issues.jboss.org/browse/JBIDE-19102 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19102) Remove org.jboss.tools.forge.runtime

by Koen Aers (JIRA)

Koen Aers created JBIDE-19102: --------------------------------- Summary: Remove org.jboss.tools.forge.runtime Key: JBIDE-19102 URL: https://issues.jboss.org/browse/JBIDE-19102 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19101) Remove F1 support

by Koen Aers (JIRA)

Koen Aers created JBIDE-19101: --------------------------------- Summary: Remove F1 support Key: JBIDE-19101 URL: https://issues.jboss.org/browse/JBIDE-19101 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.3.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19091) Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19091?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19091: --------------------------------------------- Does this happen for *any* kind of app or only specific apps ? in any case, this bug and fix does looks like something that definitely make sense to include into 8.1 IMO. > Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-19091 > URL: https://issues.jboss.org/browse/JBIDE-19091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.2.2.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > > Both SWT and JavaFX are affected. > Stack trace for javaFx web engine: > {code} > Exception in thread "JavaFX Application Thread" org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.widgets.Widget.error(Widget.java:476) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348) > at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1075) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector.inject(RippleInjector.java:68) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector.access$1(RippleInjector.java:55) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector$1.run(RippleInjector.java:44) > at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:301) > at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:298) > at java.security.AccessController.doPrivileged(Native Method) > at com.sun.javafx.application.PlatformImpl$6.run(PlatformImpl.java:298) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91) > {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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19096: --------------------------------------------- Here is a mockup of one suggestion to handle the multiple auth mechanics > 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: 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19096: --------------------------------------------- "most likely require OAuth" - are we sure it wont also be needing to support various sign ins like v2 ? About UI this is unfortunately going to be a bit tricky, but if we need to support multiple auth mechanics anyways its needed. We don't yet have a default openshift 3 server url, but how about we assume we will get one then instead of just having one default server checkbox we add the default servers to the combo and have it remember the last one used. i.e. once we have a default online url there will be "default OpenShift v2 server" and "default OpensShift v3 server" entries into this dialog which will leave the host part empty in the preference to signal it should be calculated based on preferences + file info like ~/.openshift/express.conf (for v2) Then the authentication part will also have to be extended to have a combo like: Authentication method with a combo which would need to somehow be offering all the options and once verifcation is executed if the url is not supporting the auth method tell the user and disable the options that are not valid. We can once the user starts entering credentials in the *background* ping the url to try detect auth methods and then filter/warn if the auth method is not supported but it has to be in the background (and cached) or on explicit verification to avoid a nasty slow dialog for entering credentials > 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: 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015