[JBoss JIRA] (JBIDE-24997) could org.jboss.tools.ws.jaxrs.core migrate to use lucene 7.1 instead of 3.5?
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24997?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24997:
------------------------------------
Noticed the TP is bad in terms of Lucene:
* org.apache.lucene.misc is not available to 6.1
* org.apache.lucene.queryparser is not available for 7.1
But was still able to provide a PR for 7.1
> could org.jboss.tools.ws.jaxrs.core migrate to use lucene 7.1 instead of 3.5?
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24997
> URL: https://issues.jboss.org/browse/JBIDE-24997
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.6.x
>
> Attachments: ws.jaxrs.core_lucene3.5.png
>
>
> According to p2, org.jboss.tools.ws.jaxrs.core depends on lucene 3.5. But the latest in Photon.0.My is 7.1. Could we move up to the latest?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26032) DevStudio 12 / Eclipse Photon does not work properly on RHEL 6
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26032?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-26032:
----------------------------------
Component/s: upstream
> DevStudio 12 / Eclipse Photon does not work properly on RHEL 6
> --------------------------------------------------------------
>
> Key: JBIDE-26032
> URL: https://issues.jboss.org/browse/JBIDE-26032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.6.x
> Environment: DevStudio 12.0.0.AM1
> Reporter: Tomáš Sedmík
> Priority: Critical
> Attachments: cairo-issue.webm
>
>
> If I run DevStudio 12.0.0.AM1 on RHEL 6.8 machine, I get the following warning.
> {code}
> ***WARNING: SWT requires Cairo 1.9.4 or newer
> ***WARNING: Detected: 1.8.8
> {code}
> There is no newer version of _cairo_ package in RHEL 6 or EPEL repositories. Therefore, I was unable to upgrade it.
> It has its consequences. For instance: DevStudio is terminated with the following error, if I switch the tab in Fuse Tooling Camel Editor (see attached screencast).
> {code}
> java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion `NOT_REACHED' failed.
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25825) Properties: Basic block should always be displayed 1st
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25825?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25825.
---------------------------------
Closing. PR is merged and Basic section is on the first place.
Verified in:
Red Hat JBoss Developer Studio
Version: 12.0.0.AM2
Build id: AM2-v20180516-1308-B2486
Build date: 20180516-1308
> Properties: Basic block should always be displayed 1st
> ------------------------------------------------------
>
> Key: JBIDE-25825
> URL: https://issues.jboss.org/browse/JBIDE-25825
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: properties
> Fix For: 4.6.0.AM2
>
> Attachments: image-2018-03-19-19-14-10-158.png, image-2018-03-19-19-17-41-770.png, image-2018-03-19-19-20-48-227.png
>
>
> # ASSERT: have an application running in OpenShift
> # EXEC: in OpenShift Explorer: select the project of your application
> # EXEC: in Properties view: select *Details* tab, look at the blocks being shown
> Result:
> 1st block being displayed is *Annotations*, 2nd is *Details*
> !image-2018-03-19-19-14-10-158.png!
> # EXEC: in Properties view: select *Builds*, select an entry, look at the details of it
> Result:
> !image-2018-03-19-19-17-41-770.png!
> # EXEC: in Properties view: select *Deployments*, select an entry, look at the details of it
> Result:
> !image-2018-03-19-19-20-48-227.png!
> Same is true for *Deployment Configs*, *Pods*, etc
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26032) DevStudio 12 / Eclipse Photon does not work properly on RHEL 6
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBIDE-26032:
------------------------------------
Summary: DevStudio 12 / Eclipse Photon does not work properly on RHEL 6
Key: JBIDE-26032
URL: https://issues.jboss.org/browse/JBIDE-26032
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.6.x
Environment: DevStudio 12.0.0.AM1
Reporter: Tomáš Sedmík
Priority: Critical
Attachments: cairo-issue.webm
If I run DevStudio 12.0.0.AM1 on RHEL 6.8 machine, I get the following warning.
{code}
***WARNING: SWT requires Cairo 1.9.4 or newer
***WARNING: Detected: 1.8.8
{code}
There is no newer version of _cairo_ package in RHEL 6 or EPEL repositories. Therefore, I was unable to upgrade it.
It has its consequences. For instance: DevStudio is terminated with the following error, if I switch the tab in Fuse Tooling Camel Editor (see attached screencast).
{code}
java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion `NOT_REACHED' failed.
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26027) Jetty FrameworkEvent ERROR for LiveReload
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26027?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26027:
------------------------------------
PR merged. TP updated. LiveReload rebuilding:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=1964
> Jetty FrameworkEvent ERROR for LiveReload
> -----------------------------------------
>
> Key: JBIDE-26027
> URL: https://issues.jboss.org/browse/JBIDE-26027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, upstream
> Affects Versions: 4.6.0.AM1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM2
>
>
> When you install LiveReload from Central in devstudio 12.0.0.AM2, there are two errors due to incompatible version of Jetty:
> {code}
> FrameworkEvent ERROR
> {code}
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1082]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.servlet; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.servlet; bundle-version="9.4.8.v20171121"
> org.eclipse.jetty.websocket.servlet [1081]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> org.eclipse.jetty.websocket.server [1080]
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.4.8,9.4.9)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.4.8.v20171121"; version="9.4.8"
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.registrar"; version:Version="1.0.0"
> org.apache.aries.spifly.dynamic.bundle [1073]
> No resolution report for the bundle. Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.processor"; version:Version="1.0.0"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.4.8.v20171121"
> Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> -> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"] and org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"] via two dependency chains.
> Chain 1:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"]
> Chain 2:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm
> org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
> import: (osgi.wiring.package=org.objectweb.asm)
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> {code}
> FrameworkEvent ERROR
> {code}
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1083]
> Unresolved requirement: Require-Bundle: org.jboss.tools.livereload.core; bundle-version="1.0.0"
> -> Bundle-SymbolicName: org.jboss.tools.livereload.core; bundle-version="1.5.1.v20170822-1705"; singleton:="true"
> org.jboss.tools.livereload.core [1082]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.servlet; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.servlet; bundle-version="9.4.8.v20171121"
> org.eclipse.jetty.websocket.servlet [1081]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> org.eclipse.jetty.websocket.server [1080]
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.4.8,9.4.9)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.4.8.v20171121"; version="9.4.8"
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.registrar"; version:Version="1.0.0"
> org.apache.aries.spifly.dynamic.bundle [1073]
> No resolution report for the bundle. Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.processor"; version:Version="1.0.0"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.4.8.v20171121"
> Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> -> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"] and org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"] via two dependency chains.
> Chain 1:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"]
> Chain 2:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm
> org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
> import: (osgi.wiring.package=org.objectweb.asm)
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[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:
------------------------------------
Also tried to enable GTK3 like this:
{code}-Denable.gtk3=1{code} but that doesn't seem to have helped either:
{code}17:10:00 (JBoss Tools Test Application:24258): Gtk-WARNING **: Negative content width -12 (allocation 1, extents 6x7) while allocating gadget (node separator, owner GtkSeparatorToolItem)
17:10:00 Unsupported Browser Type: SWT.MOZILLA style is deprecated.
17:10:00 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
17:10:00
17:10:00 !ENTRY org.jboss.tools.vpe.preview.core 4 0 2018-05-19 17:09:58.884
17:10:00 !MESSAGE Could not open the Visual Page Editor:
17:10:00 nsIWebBrowser is not available
17:10:00 !STACK 0
17:10:00 org.jboss.tools.vpe.xulrunner.XulRunnerException: nsIWebBrowser is not available
17:10:00 at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:127)
17:10:00 at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128)
17:10:00 at org.jboss.tools.vpe.editor.mozilla.XulRunnerEditor2.<init>(XulRunnerEditor2.java:23)
17:10:00 at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:599)
17:10:00 at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:813)
17:10:00 at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:283)
17:10:00 at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077)
17:10:00 at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:511){code}
-- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
and
{code}
!ENTRY org.jboss.tools.vpe.preview.core 4 0 2018-05-19 17:09:58.884
!MESSAGE Could not open the Visual Page Editor:
nsIWebBrowser is not available
!STACK 0
org.jboss.tools.vpe.xulrunner.XulRunnerException: nsIWebBrowser is not available{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
> 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
[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:
Two validator IDs are referenced which do not exist.
{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}
As seen in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> 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
> Fix For: 4.6.0.AM2
>
>
> Two validator IDs are referenced which do not exist.
> {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
[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)
Nick Boldt created JBIDE-26031:
----------------------------------
Summary: 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}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months