[JBoss JIRA] (ERT-753) [GTK] Make "Print Selection" work [EBZ#299550]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-753?page=com.atlassian.jira.plugin.sy... ]
Eric Williams resolved ERT-753.
-------------------------------
Resolution: Done
> [GTK] Make "Print Selection" work [EBZ#299550]
> ----------------------------------------------
>
> Key: ERT-753
> URL: https://issues.jboss.org/browse/ERT-753
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: 4.14_M1, SWT, bzira
>
> Since gtk bug http://bugzilla.gnome.org/show_bug.cgi?id=344519
> has now been fixed, we should use this feature in the GTK print dialog.
> We need to show the "Selection" radio by default when the dialog is opened, and then we need to set and get the value of the radio before and after the PrintDialog is opened.
> I believe the new radio will show up if you set gtk_print_unix_dialog_set_support_selection(true)
> Then, if the scope in our PrinterData is set to PrinterData.SELECTION, we need to set (and get) GTK_PRINT_PAGES_SELECTION in the gtk_print_settings_print_pages field of the gtk_print_settings struct.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (ERT-758) [GTK] Ability to place not digit characters to DateTime [EBZ#550501]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-758?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-758:
---------------------------------
Sprint: devex #172 Sep 2019
Assignee: Eric Williams
> [GTK] Ability to place not digit characters to DateTime [EBZ#550501]
> --------------------------------------------------------------------
>
> Key: ERT-758
> URL: https://issues.jboss.org/browse/ERT-758
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: 4.14_M1, SWT, bzira
>
> Debian Stretch
> GTK 3.22.30
> Eclipse SDK 4.12M3.
> I think, that it is a bug, when user able to place some not digit characters to DateTime widget.
> And if it is a feature, when i should say, that where is another bug: when i place some cyrillyc characters it writes some arabic characters instead.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (JBIDE-26847) An internal error occurred during: "Identify jrt-fs.jar".
by Banaan Banaan (Jira)
Banaan Banaan created JBIDE-26847:
-------------------------------------
Summary: An internal error occurred during: "Identify jrt-fs.jar".
Key: JBIDE-26847
URL: https://issues.jboss.org/browse/JBIDE-26847
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.12.0.Final, 4.11.0.Final, 4.13.x
Reporter: Banaan Banaan
I've installed
JBoss Maven Integration 1.9.3.v20190827-1345 org.jboss.tools.maven.feature.feature.group Red Hat
And when I open anything from the Java class library I get a popup with the message:
*An internal error occurred during: "Identify jrt-fs.jar".*
I don't have the full class library of the java runtime committed to my memory, so I have to look at the source quite often and this popup is getting literally in the way.
{code:java}
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBContext
at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.searchArtifactFromRemoteNexusRepository(NexusRepositoryIdentifier.java:96)
at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.getArtifactFromRemoteNexusRepository(NexusRepositoryIdentifier.java:78)
at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.identify(NexusRepositoryIdentifier.java:50)
at org.jboss.tools.maven.core.internal.identification.FileIdentificationManager.identify(FileIdentificationManager.java:91)
at org.jboss.tools.maven.sourcelookup.ui.actions.AttachSourcesActionDelegate$1.run(AttachSourcesActionDelegate.java:114)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBContext cannot be found by org.jboss.tools.maven.core_1.9.3.v20190827-1345
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:514)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:425)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:155)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 6 more
{code}
It was reported in https://issues.jboss.org/browse/JBIDE-26571, apparently not fixed in https://issues.jboss.org/browse/JBIDE-26500 as the latest SNAPSHOT plugins still exhibit this error (in 2019.9)
This is the set of JBoss Tools Maven plugins I have installed:
JBoss Maven Integration 1.9.3.v20190827-1345 org.jboss.tools.maven.feature.feature.group Red Hat
m2e - Maven Integration for Eclipse (includes Incubating components) 1.13.0.20190716-1624 org.eclipse.m2e.feature.feature.group Eclipse.org - m2e
m2e-wtp - Maven Integration for WTP 1.4.2.20190530-0057 org.eclipse.m2e.wtp.feature.feature.group Eclipse.org - m2e-wtp
Maven SCM Handler for EGit 0.15.1.201806191431 org.sonatype.m2e.egit.feature.feature.group Sonatype, Inc.
JBoss Tools Maven Packaging Configurator 1.9.3.v20190827-1345 org.jboss.tools.maven.jbosspackaging.feature.feature.group Red Hat
JBoss Tools Maven Source Lookup 1.9.3.v20190827-1345 org.jboss.tools.maven.sourcelookup.feature.feature.group Red Hat
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (JBIDE-26846) Update WildFly to version 18 in maven.itests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26846?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26846:
------------------------------------
Description:
h2. Complete the following tasks to upgrade WildFly in maven.itests to version 18:
* Update WildFly version to version 18 in examples.wildfly.itests
was:
h2. Complete the following tasks to upgrade WildFly in maven.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 WildFly to version 18 in maven.itests
> --------------------------------------------
>
> Key: JBIDE-26846
> URL: https://issues.jboss.org/browse/JBIDE-26846
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: maven
> 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 maven.itests to version 18:
> * Update WildFly version to version 18 in examples.wildfly.itests
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (JBIDE-26846) Update WildFly to version 18 in maven.itests
by Zbyněk Červinka (Jira)
Zbyněk Červinka created JBIDE-26846:
---------------------------------------
Summary: Update WildFly to version 18 in maven.itests
Key: JBIDE-26846
URL: https://issues.jboss.org/browse/JBIDE-26846
Project: Tools (JBoss Tools)
Issue Type: Component Upgrade
Components: maven
Affects Versions: 4.12.0.Final
Environment: All OSes
Reporter: Zbyněk Červinka
Assignee: Zbyněk Červinka
h2. Complete the following tasks to upgrade WildFly in maven.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
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[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:
------------------------------------
Environment: All OSes (was: All supported OS.)
> 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
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[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:
------------------------------------
Description:
h2. Complete the following tasks to upgrade WildFly version 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
was:
h2. Perform the following tasks to fully upgrade WildFly version 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 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 supported OS.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> h2. Complete the following tasks to upgrade WildFly version 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
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[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:
------------------------------------
Description:
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
was:
h2. Complete the following tasks to upgrade WildFly version 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 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 supported OS.
> 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
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years