August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20438) Use of clientBehavior tag in composite component produces warning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20438?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20438: -------------------------------------- Assignee: Viacheslav Kabanovich > Use of clientBehavior tag in composite component produces warning > ------------------------------------------------------------------ > > Key: JBIDE-20438 > URL: https://issues.jboss.org/browse/JBIDE-20438 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.3.Final > Environment: Win 7 64, Eclipse Luna 64, JDK8 64 > Reporter: Rainer Schön > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.x > > > The use of a clientBehavior tag in a composite component produces a [Unknown composite component "clientBehavior"] warning > Possible solution: Check the jboss internal tagblib: composite.taglib.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20438) Use of clientBehavior tag in composite component produces warning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20438?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20438: ----------------------------------- Fix Version/s: 4.3.x > Use of clientBehavior tag in composite component produces warning > ------------------------------------------------------------------ > > Key: JBIDE-20438 > URL: https://issues.jboss.org/browse/JBIDE-20438 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.3.Final > Environment: Win 7 64, Eclipse Luna 64, JDK8 64 > Reporter: Rainer Schön > Priority: Minor > Fix For: 4.3.x > > > The use of a clientBehavior tag in a composite component produces a [Unknown composite component "clientBehavior"] warning > Possible solution: Check the jboss internal tagblib: composite.taglib.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20437) EL syntax error when map dot notation is used in conjunction with a named CDI instance

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20437?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20437: -------------------------------------- Assignee: Viacheslav Kabanovich > EL syntax error when map dot notation is used in conjunction with a named CDI instance > -------------------------------------------------------------------------------------- > > Key: JBIDE-20437 > URL: https://issues.jboss.org/browse/JBIDE-20437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.2.3.Final > Environment: win 7 64, eclipse luna 64, jdk8 64 > Reporter: Rainer Schön > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.x > > > Dot notation for a map produces a ["xxx" cannot be resolved] warning -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20437) EL syntax error when map dot notation is used in conjunction with a named CDI instance

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20437?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20437: ----------------------------------- Fix Version/s: 4.3.x > EL syntax error when map dot notation is used in conjunction with a named CDI instance > -------------------------------------------------------------------------------------- > > Key: JBIDE-20437 > URL: https://issues.jboss.org/browse/JBIDE-20437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.2.3.Final > Environment: win 7 64, eclipse luna 64, jdk8 64 > Reporter: Rainer Schön > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.x > > > Dot notation for a map produces a ["xxx" cannot be resolved] warning -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20439) Tooltip in xhtml editor does not format correctly

by Rainer Schön (JIRA)

Rainer Schön created JBIDE-20439: ------------------------------------ Summary: Tooltip in xhtml editor does not format correctly Key: JBIDE-20439 URL: https://issues.jboss.org/browse/JBIDE-20439 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html-source-editing Affects Versions: 4.2.3.Final Environment: Win7 64, Eclipse Luna 64, JDK8 64 Reporter: Rainer Schön Priority: Minor The pop up hint does not format the usual way (yellow background, small font). The window has a white background and normal sized font -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20022) As a user I want to easily get to the web-console

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20022?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20022: ------------------------------------------ this was review, merged and pushed. resolving. > As a user I want to easily get to the web-console > ------------------------------------------------- > > Key: JBIDE-20022 > URL: https://issues.jboss.org/browse/JBIDE-20022 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > When in Eclipse I would like to be able to easily open the web console for my connection. > Ideally this would be an item present in the context menu of a connection Show In->Web Console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20438) Use of clientBehavior tag in composite component produces warning

by Rainer Schön (JIRA)

Rainer Schön created JBIDE-20438: ------------------------------------ Summary: Use of clientBehavior tag in composite component produces warning Key: JBIDE-20438 URL: https://issues.jboss.org/browse/JBIDE-20438 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.2.3.Final Environment: Win 7 64, Eclipse Luna 64, JDK8 64 Reporter: Rainer Schön Priority: Minor The use of a clientBehavior tag in a composite component produces a [Unknown composite component "clientBehavior"] warning Possible solution: Check the jboss internal tagblib: composite.taglib.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20372) Connection wizard: selecting Openshift v3 unchecks "Use default Server" but does not clear server url

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20372?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20372: ------------------------------------- Labels: application_wizard openshift_v3 (was: application_wizard help_wanted openshift_v3) > Connection wizard: selecting Openshift v3 unchecks "Use default Server" but does not clear server url > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20372 > URL: https://issues.jboss.org/browse/JBIDE-20372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > When creating a new OpenShift Application, if you select OpenShift 3, the "Use Default Server" checkbox is unchecked but the "Server" is not cleared, https://openshift.redhat.com which was set since the connection wizard defaults to v2 and openshift.redhat.com is the default server for v2, is not cleared. > The default value for v3 should be empty, until Openshift 3 gets a public url. > A default property could be set in https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j..., then updated asynchronously without rebuilding the openshift plugin -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20372) Connection wizard: selecting Openshift v3 unchecks "Use default Server" but does not clear server url

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20372?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20372: ---------------------------------------- Assignee: Andre Dietisheim Resolution: Done > Connection wizard: selecting Openshift v3 unchecks "Use default Server" but does not clear server url > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20372 > URL: https://issues.jboss.org/browse/JBIDE-20372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: application_wizard, help_wanted, openshift_v3 > Fix For: 4.3.0.CR1 > > > When creating a new OpenShift Application, if you select OpenShift 3, the "Use Default Server" checkbox is unchecked but the "Server" is not cleared, https://openshift.redhat.com which was set since the connection wizard defaults to v2 and openshift.redhat.com is the default server for v2, is not cleared. > The default value for v3 should be empty, until Openshift 3 gets a public url. > A default property could be set in https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j..., then updated asynchronously without rebuilding the openshift plugin -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20372) Connection wizard: selecting Openshift v3 unchecks "Use default Server" but does not clear server url

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20372?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20372: ------------------------------------------ I tested it, it works for me. Thanks! rebased, merged and pushed to upstream/master > Connection wizard: selecting Openshift v3 unchecks "Use default Server" but does not clear server url > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20372 > URL: https://issues.jboss.org/browse/JBIDE-20372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > When creating a new OpenShift Application, if you select OpenShift 3, the "Use Default Server" checkbox is unchecked but the "Server" is not cleared, https://openshift.redhat.com which was set since the connection wizard defaults to v2 and openshift.redhat.com is the default server for v2, is not cleared. > The default value for v3 should be empty, until Openshift 3 gets a public url. > A default property could be set in https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j..., then updated asynchronously without rebuilding the openshift plugin -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 August 2015