[JBoss JIRA] (ERT-750) [GTK3] Composite receives to much repaint events [EBZ#546248]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-750?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-750:
---------------------------------
Sprint: devex #170 Aug 2019
Assignee: Eric Williams
> [GTK3] Composite receives to much repaint events [EBZ#546248]
> -------------------------------------------------------------
>
> Key: ERT-750
> URL: https://issues.jboss.org/browse/ERT-750
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Please launch the attached snippet. 1 or 2 Paint events occur. If you move the mouse over the window, it will show some MouseMove events followed by Paint events. But
> a) a lot of Paint events occur between having moved the mouse and the MouseHover event occurs, and
> b) up to 3s after the MouseHover event occurred, a lot of Paint events are received.
> 4:29:52 PM: p
> 4:29:53 PM: mpmpmpmpmpmpmppp
> 4:29:53 PM: ppppppppppppppp
> 4:29:53 PM: ppppppphpppppppp
> 4:29:54 PM: ppppppppppppppp
> 4:29:54 PM: ppppppp
> 4:29:55 PM: ppppppppp
> 4:29:55 PM: ppppppppppppppp
> 4:29:55 PM: ppppppppppppppp
> 4:29:56 PM: ppppppppppppppp
> 4:29:56 PM: pppppp
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (ERT-750) [GTK3] Composite receives to much repaint events [EBZ#546248]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-750?page=com.atlassian.jira.plugin.sy... ]
Eric Williams resolved ERT-750.
-------------------------------
Resolution: Done
> [GTK3] Composite receives to much repaint events [EBZ#546248]
> -------------------------------------------------------------
>
> Key: ERT-750
> URL: https://issues.jboss.org/browse/ERT-750
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Please launch the attached snippet. 1 or 2 Paint events occur. If you move the mouse over the window, it will show some MouseMove events followed by Paint events. But
> a) a lot of Paint events occur between having moved the mouse and the MouseHover event occurs, and
> b) up to 3s after the MouseHover event occurred, a lot of Paint events are received.
> 4:29:52 PM: p
> 4:29:53 PM: mpmpmpmpmpmpmppp
> 4:29:53 PM: ppppppppppppppp
> 4:29:53 PM: ppppppphpppppppp
> 4:29:54 PM: ppppppppppppppp
> 4:29:54 PM: ppppppp
> 4:29:55 PM: ppppppppp
> 4:29:55 PM: ppppppppppppppp
> 4:29:55 PM: ppppppppppppppp
> 4:29:56 PM: ppppppppppppppp
> 4:29:56 PM: pppppp
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (ERT-750) [GTK3] Composite receives to much repaint events [EBZ#546248]
by Friendly Jira Robot (Jira)
Friendly Jira Robot created ERT-750:
---------------------------------------
Summary: [GTK3] Composite receives to much repaint events [EBZ#546248]
Key: ERT-750
URL: https://issues.jboss.org/browse/ERT-750
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
Please launch the attached snippet. 1 or 2 Paint events occur. If you move the mouse over the window, it will show some MouseMove events followed by Paint events. But
a) a lot of Paint events occur between having moved the mouse and the MouseHover event occurs, and
b) up to 3s after the MouseHover event occurred, a lot of Paint events are received.
4:29:52 PM: p
4:29:53 PM: mpmpmpmpmpmpmppp
4:29:53 PM: ppppppppppppppp
4:29:53 PM: ppppppphpppppppp
4:29:54 PM: ppppppppppppppp
4:29:54 PM: ppppppp
4:29:55 PM: ppppppppp
4:29:55 PM: ppppppppppppppp
4:29:55 PM: ppppppppppppppp
4:29:56 PM: ppppppppppppppp
4:29:56 PM: pppppp
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26656) Start sending UMB messages for jbosstools aggregate build
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26656?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26656:
----------------------------------
Fix Version/s: 4.13.0.AM1
(was: 4.13.x)
> Start sending UMB messages for jbosstools aggregate build
> ---------------------------------------------------------
>
> Key: JBIDE-26656
> URL: https://issues.jboss.org/browse/JBIDE-26656
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.12.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: jenkins, qa, quality
> Fix For: 4.13.0.AM1
>
>
> As a part of QE - CI initiative is to provide unified process of sending build notifications for other possible consumers of our product, we should prepare specification for unified message bus (JBIDE-26652) and assure that product/project build jobs send proper messages.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) See the error in the beans.xml file similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
<weld:exclude name="exclude.p2.*">
<weld:if-system-property name="verbosity" value="low"/>
</weld:exclude>
<weld:exclude name="exclude.p4.**">
<weld:if-class-available name="exclude.p4.Bean5"/>
<weld:if-class-available name="!exclude.p6.DoesNotExist"/>
</weld:exclude>
<weld:exclude name="exclude.p6.**">
<weld:if-class-available name="exclude.p6.DoesNotExist"/>
</weld:exclude>
</weld:scan>
</beans>
{code}
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
<weld:exclude name="exclude.p2.*">
<weld:if-system-property name="verbosity" value="low"/>
</weld:exclude>
<weld:exclude name="exclude.p4.**">
<weld:if-class-available name="exclude.p4.Bean5"/>
<weld:if-class-available name="!exclude.p6.DoesNotExist"/>
</weld:exclude>
<weld:exclude name="exclude.p6.**">
<weld:if-class-available name="exclude.p6.DoesNotExist"/>
</weld:exclude>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_2_0.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26793:
------------------------------------
Steps to Reproduce:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
<weld:exclude name="exclude.p2.*">
<weld:if-system-property name="verbosity" value="low"/>
</weld:exclude>
<weld:exclude name="exclude.p4.**">
<weld:if-class-available name="exclude.p4.Bean5"/>
<weld:if-class-available name="!exclude.p6.DoesNotExist"/>
</weld:exclude>
<weld:exclude name="exclude.p6.**">
<weld:if-class-available name="exclude.p6.DoesNotExist"/>
</weld:exclude>
</weld:scan>
</beans>
{code}
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) See the error similar to the one captured on the *beans-xml.png* image in the attachment
was:
1) Create new CDI 2.0 Web Project (remember to set the CDI to value 2.0 and java to version 1.8)
2) Go to beans.xml and set the *Bean-Discovery-Mode* to *all*
3) Create new package with name *exclude.p1*
4) Create new Bean with name *Bean1*
5) Change the content of the beans.xml file to:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<beans bean-discovery-mode="all" version="2.0"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:weld="http://jboss.org/schema/weld/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
<weld:scan>
<weld:exclude name="exclude.p1.Bean1"/>
<weld:exclude name="exclude.p2.*">
<weld:if-system-property name="verbosity" value="low"/>
</weld:exclude>
<weld:exclude name="exclude.p4.**">
<weld:if-class-available name="exclude.p4.Bean5"/>
<weld:if-class-available name="!exclude.p6.DoesNotExist"/>
</weld:exclude>
<weld:exclude name="exclude.p6.**">
<weld:if-class-available name="exclude.p6.DoesNotExist"/>
</weld:exclude>
</weld:scan>
</beans>
{code}
6) See the error similar to the one captured on the *beans-xml.png* image in the attachment
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months