May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22414) Server editor: closing it before the widgets are enabled ends up in "widget disposed" error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22414?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22414: ------------------------------------- Component/s: common/jst/core > Server editor: closing it before the widgets are enabled ends up in "widget disposed" error > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22414 > URL: https://issues.jboss.org/browse/JBIDE-22414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-715) Add the attribute 'destination name' into SAP configuration

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-715: --------------------------------------- Summary: Add the attribute 'destination name' into SAP configuration Key: JBTIS-715 URL: https://issues.jboss.org/browse/JBTIS-715 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Add the attribute 'destination name' into SAP configuration. This is a mandatory attribute when specifying a server. At the moment, the logic is implemented inside SAP tests. Moreover, allow to specify more destinations and servers the appripriate XML schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22422) UI inconsistency in Deploy Docker image

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22422?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22422: ------------------------------- Story Points: 4 > UI inconsistency in Deploy Docker image > --------------------------------------- > > Key: JBIDE-22422 > URL: https://issues.jboss.org/browse/JBIDE-22422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Fix For: 4.4.x > > > When invoked from the Docker explorer, it is not possible to create a new Openshift connection. > When invoked from the Openshift explorer, it is possible to create a new Docker connection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22412) Enhance JobChainBuilder with conditions for starting the next job

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22412: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 > Enhance JobChainBuilder with conditions for starting the next job > ----------------------------------------------------------------- > > Key: JBIDE-22412 > URL: https://issues.jboss.org/browse/JBIDE-22412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > For example, if the chain of jobs is loading content of a wizard or an editor, and user may close it before jobs are completed, there is no need to schedule the next job in the chain when the previous job is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22412) Enhance JobChainBuilder with conditions for starting the next job

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22412?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22412: ------------------------------------------ [~scabanovich] can you take care of this one, too since it's closely related to your piror work in JBIDE-22379? > Enhance JobChainBuilder with conditions for starting the next job > ----------------------------------------------------------------- > > Key: JBIDE-22412 > URL: https://issues.jboss.org/browse/JBIDE-22412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > For example, if the chain of jobs is loading content of a wizard or an editor, and user may close it before jobs are completed, there is no need to schedule the next job in the chain when the previous job is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22422) UI inconsistency in Deploy Docker image

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22422: ---------------------------------- Summary: UI inconsistency in Deploy Docker image Key: JBIDE-22422 URL: https://issues.jboss.org/browse/JBIDE-22422 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha2 Reporter: Jeff MAURY Fix For: 4.4.x When invoked from the Docker explorer, it is not possible to create a new Openshift connection. When invoked from the Openshift explorer, it is possible to create a new Docker connection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21220) Incorrect JSF Phase Listener Warning

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21220?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21220. --------------------------------- Verified in Red Hat Developer Studio with build id: Alpha1-v20160520-0424-B5396. > Incorrect JSF Phase Listener Warning > ------------------------------------ > > Key: JBIDE-21220 > URL: https://issues.jboss.org/browse/JBIDE-21220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.0.Final > Environment: Mars.1 > Java 8 > Reporter: Cody Lerum > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > When adding a JSF phase listener to faces-config.xml > {code} > <lifecycle> > <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener> > </lifecycle> > {code} > You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}} > In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html > In java 8 at least you get a compiler error if you try and extend avax.faces.event.PhaseListener. > The type PhaseListener cannot be the superclass of JsfCdiPhaseListener; a superclass must be a class -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21058) JSF tests fail

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21058?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21058. --------------------------------- > JSF tests fail > -------------- > > Key: JBIDE-21058 > URL: https://issues.jboss.org/browse/JBIDE-21058 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > Multiple failures are caused by > java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.jsf.ui.JsfUiPlugin$PluginHolder > because of class cast exception at > (JsfUiPlugin)Platform.getPlugin(PLUGIN_ID) > since platform returned DefaultPlugin instead of JsfUiPlugin. > Method Platform.getPlugin(String) is deprecated and probably works in the latest Eclipse not as before. Multiple failures (80 and more) started with build #52 on October 25, 2015. Build #51had only few failed tests. > Pattern of initializing JsfUiPlugin is very uncommon and we should change it to the regular pattern in which static plugin instance is set in the constructor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22413) Connection Editor: dont launch further jobs if editor is already closed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22413?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22413: ------------------------------------------ [~scabanovich] can you take care of this one, too since it's closely related to your piror work in JBIDE-22379? > Connection Editor: dont launch further jobs if editor is already closed > ----------------------------------------------------------------------- > > Key: JBIDE-22413 > URL: https://issues.jboss.org/browse/JBIDE-22413 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > ASSERT: make sure that you have a server adapter > EXEC: open it in the server editor > ASSERT: the widgets in the openshift section are disabled, in the status bar (or progress view) you see a job "Loading projects..." running > EXEC: close the editor > ASSERT: nothing happens so far, but you see another job running "Setting connection, deploy..." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22413) Connection Editor: dont launch further jobs if editor is already closed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22413?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22413: ---------------------------------------- Assignee: Viacheslav Kabanovich > Connection Editor: dont launch further jobs if editor is already closed > ----------------------------------------------------------------------- > > Key: JBIDE-22413 > URL: https://issues.jboss.org/browse/JBIDE-22413 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > ASSERT: make sure that you have a server adapter > EXEC: open it in the server editor > ASSERT: the widgets in the openshift section are disabled, in the status bar (or progress view) you see a job "Loading projects..." running > EXEC: close the editor > ASSERT: nothing happens so far, but you see another job running "Setting connection, deploy..." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016