[JBoss JIRA] (JBIDE-26750) Update CDI.itests to run on java 11 and add some parameters to the pom.xml
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26750?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26750:
------------------------------------
Description:
*Description of the task from [~odockal]:*
It would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11.
Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method? Let's put it into some utility class, that's an easiest solution.
Update:
I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once.
And you can run test for both server eap and wildfly driven by param in jenkins.
was:
*Description of the task from [~odockal]:*
As I said some time ago, would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11. Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method?
Let's put it into some utility class, that's an easiest solution.
Update:
I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once.
And you can run test for both server eap and wildfly driven by param in jenkins.
> Update CDI.itests to run on java 11 and add some parameters to the pom.xml
> --------------------------------------------------------------------------
>
> Key: JBIDE-26750
> URL: https://issues.jboss.org/browse/JBIDE-26750
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi
> Affects Versions: 4.13.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.13.0.Final
>
>
> *Description of the task from [~odockal]:*
> It would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11.
> Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method? Let's put it into some utility class, that's an easiest solution.
> Update:
> I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once.
> And you can run test for both server eap and wildfly driven by param in jenkins.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26845) Update WildFly to version 18 in examples.wildfly.itests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26845?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26845:
------------------------------------
Story Points: 8 (was: 5)
> Update WildFly to version 18 in examples.wildfly.itests
> -------------------------------------------------------
>
> Key: JBIDE-26845
> URL: https://issues.jboss.org/browse/JBIDE-26845
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: project-examples
> Affects Versions: 4.12.0.Final
> Environment: All OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> h2. Complete the following tasks to upgrade WildFly in examples.wildfly.itests to version 18:
> * Update WildFly version to version 18 in examples.wildfly.itests
> * Check and update entries in the *wildfly-blacklist* file
> * Check and update entries in the *wildfly-blacklist-test-errors-regexes.json* file
> * Update all WildFly quickstart JIRAs (extend all jiras by current state description and resolve all jiras, where the issue has been resolved)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ERT-765) [GTK] Nothing is rendered when creating new GC on canvas [EBZ#551982]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-765?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-765:
---------------------------------
Sprint: devex #174 Oct 2019
Assignee: Eric Williams
> [GTK] Nothing is rendered when creating new GC on canvas [EBZ#551982]
> ---------------------------------------------------------------------
>
> Key: ERT-765
> URL: https://issues.jboss.org/browse/ERT-765
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: 4.14_M3, SWT, bzira
>
> This is example from http://www.java2s.com/Tutorial/Java/0300__SWT-2D-Graphics/Graphics.htm
> It shows empty window when run on Ubuntu 18.04 with open jdk 1.8
> Mac and Windows works fine.
> Also works if use e.gc instead of new GC(...)
> It used to work before
> Swt used
> org.eclipse.swt.gtk.linux.x86_64_3.111.0.v20190605-1801.jar
> import org.eclipse.swt.SWT;
> import org.eclipse.swt.events.PaintEvent;
> import org.eclipse.swt.events.PaintListener;
> import org.eclipse.swt.graphics.GC;
> import org.eclipse.swt.layout.FillLayout;
> import org.eclipse.swt.widgets.Canvas;
> import org.eclipse.swt.widgets.Display;
> import org.eclipse.swt.widgets.Shell;
> public class GCCreateFrom {
> public static void main(String[] args) {
> Display display = new Display();
> Shell shell = new Shell(display);
> shell.setText("Canvas Example");
> shell.setLayout(new FillLayout());
> final Canvas canvas = new Canvas(shell, SWT.NONE);
> canvas.addPaintListener(new PaintListener() {
> @Override
> public void paintControl(PaintEvent e) {
> GC gc = new GC(canvas);
> gc.setForeground(e.display.getSystemColor(SWT.COLOR_RED));
> gc.drawFocus(5, 5, 200, 10);
> gc.drawText("You can draw text directly on a canvas", 60, 60);
> gc.dispose();
> }
> });
> shell.open();
> while (!shell.isDisposed()) {
> if (!display.readAndDispatch()) {
> display.sleep();
> }
> }
> display.dispose();
> }
> }
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ERT-765) [GTK] Nothing is rendered when creating new GC on canvas [EBZ#551982]
by Friendly Jira Robot (Jira)
Friendly Jira Robot created ERT-765:
---------------------------------------
Summary: [GTK] Nothing is rendered when creating new GC on canvas [EBZ#551982]
Key: ERT-765
URL: https://issues.jboss.org/browse/ERT-765
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
This is example from http://www.java2s.com/Tutorial/Java/0300__SWT-2D-Graphics/Graphics.htm
It shows empty window when run on Ubuntu 18.04 with open jdk 1.8
Mac and Windows works fine.
Also works if use e.gc instead of new GC(...)
It used to work before
Swt used
org.eclipse.swt.gtk.linux.x86_64_3.111.0.v20190605-1801.jar
import org.eclipse.swt.SWT;
import org.eclipse.swt.events.PaintEvent;
import org.eclipse.swt.events.PaintListener;
import org.eclipse.swt.graphics.GC;
import org.eclipse.swt.layout.FillLayout;
import org.eclipse.swt.widgets.Canvas;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
public class GCCreateFrom {
public static void main(String[] args) {
Display display = new Display();
Shell shell = new Shell(display);
shell.setText("Canvas Example");
shell.setLayout(new FillLayout());
final Canvas canvas = new Canvas(shell, SWT.NONE);
canvas.addPaintListener(new PaintListener() {
@Override
public void paintControl(PaintEvent e) {
GC gc = new GC(canvas);
gc.setForeground(e.display.getSystemColor(SWT.COLOR_RED));
gc.drawFocus(5, 5, 200, 10);
gc.drawText("You can draw text directly on a canvas", 60, 60);
gc.dispose();
}
});
shell.open();
while (!shell.isDisposed()) {
if (!display.readAndDispatch()) {
display.sleep();
}
}
display.dispose();
}
}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26817:
------------------------------------
Attachment: RHCRS-2019-10-16 v 17.10.09.png
> link to "Get involved" shows the page for CAT that was suspended in 2016
> ------------------------------------------------------------------------
>
> Key: JBIDE-26817
> URL: https://issues.jboss.org/browse/JBIDE-26817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.13.0.Final
>
> Attachments: RHCRS-2019-10-16 v 17.10.09.png, central.png, image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png, page_with_cat.png
>
>
> steps:
> # ASSERT: have central opened
> # EXEC: click on the link "Get involved"
> !image-2019-09-09-21-39-10-326.png!
> result:
> browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016*
> !image-2019-09-09-21-40-21-204.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka edited comment on JBIDE-26817 at 10/16/19 11:19 AM:
--------------------------------------------------------------------
I have good news for everybody - now it finally works for me also:
!RHCRS-2019-10-16 v 17.10.09.png|thumbnail!
h3. Tested in Red Hat CodeReady Studio:
Version: 12.13.0.GA
Build id: GA-v20191016-0424-B5159
Build date: 20191016-0424
was (Author: zcervink):
I have good news for everybody - now it finally works for me also.
h3. Tested in Red Hat CodeReady Studio:
Version: 12.13.0.GA
Build id: GA-v20191016-0424-B5159
Build date: 20191016-0424
> link to "Get involved" shows the page for CAT that was suspended in 2016
> ------------------------------------------------------------------------
>
> Key: JBIDE-26817
> URL: https://issues.jboss.org/browse/JBIDE-26817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.13.0.Final
>
> Attachments: RHCRS-2019-10-16 v 17.10.09.png, central.png, image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png, page_with_cat.png
>
>
> steps:
> # ASSERT: have central opened
> # EXEC: click on the link "Get involved"
> !image-2019-09-09-21-39-10-326.png!
> result:
> browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016*
> !image-2019-09-09-21-40-21-204.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26845) Update WildFly to version 18 in examples.wildfly.itests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26845?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26845:
------------------------------------
Sprint: devex #174 Oct 2019
> Update WildFly to version 18 in examples.wildfly.itests
> -------------------------------------------------------
>
> Key: JBIDE-26845
> URL: https://issues.jboss.org/browse/JBIDE-26845
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: project-examples
> Affects Versions: 4.12.0.Final
> Environment: All OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> h2. Complete the following tasks to upgrade WildFly in examples.wildfly.itests to version 18:
> * Update WildFly version to version 18 in examples.wildfly.itests
> * Check and update entries in the *wildfly-blacklist* file
> * Check and update entries in the *wildfly-blacklist-test-errors-regexes.json* file
> * Update all WildFly quickstart JIRAs (extend all jiras by current state description and resolve all jiras, where the issue has been resolved)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months