May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26031) org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26031?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26031: ------------------------------- Description: {code} 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} {code} 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} As seen in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was: {code} 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} {code} 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} > org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26031 > URL: https://issues.jboss.org/browse/JBIDE-26031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} > As seen in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26031) org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26031?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26031: ---------------------------------- Assignee: Jeff MAURY > org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26031 > URL: https://issues.jboss.org/browse/JBIDE-26031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} > As seen in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26030) VPE tests times out due to SWT on GTK 2.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26030?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26030: ---------------------------------- Assignee: Jeff MAURY > VPE tests times out due to SWT on GTK 2.x > ----------------------------------------- > > Key: JBIDE-26030 > URL: https://issues.jboss.org/browse/JBIDE-26030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, visual-page-editor-templates > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.0.AM2 > > > We've been having this problem for a while now with the VPE builds: > {code} > !MESSAGE Could not open the Visual Page Editor: > No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > !STACK 0 > org.eclipse.swt.SWTError: No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > at org.eclipse.swt.SWT.error(SWT.java:4578) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:125) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:123) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128){code} > from https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26030) VPE tests times out due to SWT on GTK 2.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26030?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26030: ------------------------------- Fix Version/s: 4.6.0.AM2 > VPE tests times out due to SWT on GTK 2.x > ----------------------------------------- > > Key: JBIDE-26030 > URL: https://issues.jboss.org/browse/JBIDE-26030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, visual-page-editor-templates > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.0.AM2 > > > We've been having this problem for a while now with the VPE builds: > {code} > !MESSAGE Could not open the Visual Page Editor: > No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > !STACK 0 > org.eclipse.swt.SWTError: No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > at org.eclipse.swt.SWT.error(SWT.java:4578) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:125) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:123) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128){code} > from https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26030) VPE tests times out due to SWT on GTK 2.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26030?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26030: ------------------------------------ Not better. Now getting this: {code} 15:54:55 Unsupported Browser Type: SWT.MOZILLA style is deprecated. 15:54:55 It'll be removed from the user specified style. Browser will be created with the modified style and if no other style bit is specified, browser with SWT.NONE style will be created 15:54:55 15:54:55 !ENTRY org.jboss.tools.vpe.preview.core 4 0 2018-05-19 15:54:53.555 15:54:55 !MESSAGE Could not open the Visual Page Editor: 15:54:55 No more handles because no underlying browser available. 15:54:55 SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. 15:54:55 15:54:55 !STACK 0 15:54:55 org.eclipse.swt.SWTError: No more handles because no underlying browser available. 15:54:55 SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API.{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > VPE tests times out due to SWT on GTK 2.x > ----------------------------------------- > > Key: JBIDE-26030 > URL: https://issues.jboss.org/browse/JBIDE-26030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, visual-page-editor-templates > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > > We've been having this problem for a while now with the VPE builds: > {code} > !MESSAGE Could not open the Visual Page Editor: > No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > !STACK 0 > org.eclipse.swt.SWTError: No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > at org.eclipse.swt.SWT.error(SWT.java:4578) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:125) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:123) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128){code} > from https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26030) VPE tests times out due to SWT on GTK 2.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26030?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26030: ------------------------------------ Trying a fix in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * set timeout to 50 mins (not 180) * `export GDK_BACKEND=x11` * `export SWT_GTK3=1` > VPE tests times out due to SWT on GTK 2.x > ----------------------------------------- > > Key: JBIDE-26030 > URL: https://issues.jboss.org/browse/JBIDE-26030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, visual-page-editor-templates > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > > We've been having this problem for a while now with the VPE builds: > {code} > !MESSAGE Could not open the Visual Page Editor: > No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > !STACK 0 > org.eclipse.swt.SWTError: No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > at org.eclipse.swt.SWT.error(SWT.java:4578) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:125) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:123) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128){code} > from https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26030) VPE tests times out due to SWT on GTK 2.x

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26030: ---------------------------------- Summary: VPE tests times out due to SWT on GTK 2.x Key: JBIDE-26030 URL: https://issues.jboss.org/browse/JBIDE-26030 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core, visual-page-editor-templates Affects Versions: 4.6.0.AM1 Reporter: Nick Boldt We've been having this problem for a while now with the VPE builds: {code} !MESSAGE Could not open the Visual Page Editor: No more handles because no underlying browser available. SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. !STACK 0 org.eclipse.swt.SWTError: No more handles because no underlying browser available. SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. at org.eclipse.swt.SWT.error(SWT.java:4578) at org.eclipse.swt.browser.Browser.<init>(Browser.java:125) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:123) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128){code} from https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26029) Incorrect warning for @Inject ServletContext

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26029: ------------------------------- Sprint: devex #150 June 2019 > Incorrect warning for @Inject ServletContext > -------------------------------------------- > > Key: JBIDE-26029 > URL: https://issues.jboss.org/browse/JBIDE-26029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.5.3.Final > Reporter: Rich DiCroce > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > If you inject ServletContext into a CDI bean, it gets flagged with this warning: > {quote} > No bean is eligible for injection to the injection point [JSR-346 §5.2.2] > {quote} > This warning appears to be correct for CDI 1.0, but not for later versions. From CDI 2.0 spec section 18.8 (also CDI 1.1/1.2 section 3.8): > {quote} > A servlet container must provide the following built-in beans, all of which have qualifier @Default: > * a bean with bean type javax.servlet.http.HttpServletRequest, allowing injection of a reference to the HttpServletRequest > * a bean with bean type javax.servlet.http.HttpSession, allowing injection of a reference to the HttpSession, > * a bean with bean type javax.servlet.ServletContext, allowing injection of a reference to the ServletContext, > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26029) Incorrect warning for @Inject ServletContext

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26029: ---------------------------------- Assignee: Jeff MAURY > Incorrect warning for @Inject ServletContext > -------------------------------------------- > > Key: JBIDE-26029 > URL: https://issues.jboss.org/browse/JBIDE-26029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.5.3.Final > Reporter: Rich DiCroce > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > If you inject ServletContext into a CDI bean, it gets flagged with this warning: > {quote} > No bean is eligible for injection to the injection point [JSR-346 §5.2.2] > {quote} > This warning appears to be correct for CDI 1.0, but not for later versions. From CDI 2.0 spec section 18.8 (also CDI 1.1/1.2 section 3.8): > {quote} > A servlet container must provide the following built-in beans, all of which have qualifier @Default: > * a bean with bean type javax.servlet.http.HttpServletRequest, allowing injection of a reference to the HttpServletRequest > * a bean with bean type javax.servlet.http.HttpSession, allowing injection of a reference to the HttpSession, > * a bean with bean type javax.servlet.ServletContext, allowing injection of a reference to the ServletContext, > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26029) Incorrect warning for @Inject ServletContext

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26029: ------------------------------- Fix Version/s: 4.6.0.AM3 > Incorrect warning for @Inject ServletContext > -------------------------------------------- > > Key: JBIDE-26029 > URL: https://issues.jboss.org/browse/JBIDE-26029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.5.3.Final > Reporter: Rich DiCroce > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > If you inject ServletContext into a CDI bean, it gets flagged with this warning: > {quote} > No bean is eligible for injection to the injection point [JSR-346 §5.2.2] > {quote} > This warning appears to be correct for CDI 1.0, but not for later versions. From CDI 2.0 spec section 18.8 (also CDI 1.1/1.2 section 3.8): > {quote} > A servlet container must provide the following built-in beans, all of which have qualifier @Default: > * a bean with bean type javax.servlet.http.HttpServletRequest, allowing injection of a reference to the HttpServletRequest > * a bean with bean type javax.servlet.http.HttpSession, allowing injection of a reference to the HttpSession, > * a bean with bean type javax.servlet.ServletContext, allowing injection of a reference to the ServletContext, > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018