[JBoss JIRA] (ERT-719) GPG key for code signing
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/ERT-719?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt commented on ERT-719:
--------------------------------
Moved from JBDS to ERT, since this is an Eclipse / devtools issue.
[~mat.booth] [~scela] [~akurtakov] FYI.
> GPG key for code signing
> ------------------------
>
> Key: ERT-719
> URL: https://issues.jboss.org/browse/ERT-719
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
> Fix For: Future
>
>
> Hi, this is related to JBDS-4740 -- allow building of flatpak applications.
> I will need to GPG sign flatpak applications before users can install them.
> Does jenkins know about any GPG keys for code signing? And if so, where does the keyring live?
> When I ran "{{gpg --list-keys}}" during a build, to list all the keys in the default keyring location (the default location is ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (ERT-719) GPG key for code signing
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/ERT-719?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt updated ERT-719:
---------------------------
Project: Eclipse Release Train (was: Red Hat CodeReady Studio (devstudio))
Key: ERT-719 (was: JBDS-4746)
Docs QE Status: (was: NEW)
Component/s: (was: build)
Fix Version/s: Future
(was: 12.x)
> GPG key for code signing
> ------------------------
>
> Key: ERT-719
> URL: https://issues.jboss.org/browse/ERT-719
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
> Fix For: Future
>
>
> Hi, this is related to JBDS-4740 -- allow building of flatpak applications.
> I will need to GPG sign flatpak applications before users can install them.
> Does jenkins know about any GPG keys for code signing? And if so, where does the keyring live?
> When I ran "{{gpg --list-keys}}" during a build, to list all the keys in the default keyring location (the default location is ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (ERT-718) [Wayland] Eclipse crashes after interaction with WebKit [EBZ#545275]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-718?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-718:
---------------------------------
Sprint: devex #164 April 2019
Assignee: Eric Williams
> [Wayland] Eclipse crashes after interaction with WebKit [EBZ#545275]
> --------------------------------------------------------------------
>
> Key: ERT-718
> URL: https://issues.jboss.org/browse/ERT-718
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Using Eclipse SDK (master) from http://eclipse.matbooth.co.uk/flatpak/ .
> Version: 2019-03 (4.11)
> Build id: I20190211-1800
> 1) Start Eclipse in a new workspace
> 2) Create a new Java project
> 3) Open the type hierarchy (ctrl+shift+t) and open java.lang.Object
> 4) Hover over the Object type defintion (or anything that might display hover info with some data)
> 5) Once the hover gets focus (ie. doesn't disappear), start double clicking quickly, while continuing to move the mouse some small distance within the bounds of the hover.
> Step 5 usually, though not consistently results in a crash.
> C [libwayland-client.so.0+0x82a4] wl_proxy_get_user_data+0x4
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> J 2507 org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(JZ)Z (0 bytes) @ 0x00007f831c574e84 [0x00007f831c574e40+0x0000000000000044]
> J 11155 c2 org.eclipse.swt.widgets.Display.readAndDispatch()Z (77 bytes) @ 0x00007f831c61b220 [0x00007f831c61af80+0x00000000000002a0]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (ERT-718) [Wayland] Eclipse crashes after interaction with WebKit [EBZ#545275]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-718?page=com.atlassian.jira.plugin.sy... ]
Eric Williams resolved ERT-718.
-------------------------------
Resolution: Done
> [Wayland] Eclipse crashes after interaction with WebKit [EBZ#545275]
> --------------------------------------------------------------------
>
> Key: ERT-718
> URL: https://issues.jboss.org/browse/ERT-718
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Using Eclipse SDK (master) from http://eclipse.matbooth.co.uk/flatpak/ .
> Version: 2019-03 (4.11)
> Build id: I20190211-1800
> 1) Start Eclipse in a new workspace
> 2) Create a new Java project
> 3) Open the type hierarchy (ctrl+shift+t) and open java.lang.Object
> 4) Hover over the Object type defintion (or anything that might display hover info with some data)
> 5) Once the hover gets focus (ie. doesn't disappear), start double clicking quickly, while continuing to move the mouse some small distance within the bounds of the hover.
> Step 5 usually, though not consistently results in a crash.
> C [libwayland-client.so.0+0x82a4] wl_proxy_get_user_data+0x4
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> J 2507 org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(JZ)Z (0 bytes) @ 0x00007f831c574e84 [0x00007f831c574e40+0x0000000000000044]
> J 11155 c2 org.eclipse.swt.widgets.Display.readAndDispatch()Z (77 bytes) @ 0x00007f831c61b220 [0x00007f831c61af80+0x00000000000002a0]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (JBIDE-26571) Java 11: An internal error occurred during: "Identify jrt-fs.jar".
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26571?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26571:
-------------------------------
Fix Version/s: 4.11.0.Final
> Java 11: An internal error occurred during: "Identify jrt-fs.jar".
> ------------------------------------------------------------------
>
> Key: JBIDE-26571
> URL: https://issues.jboss.org/browse/JBIDE-26571
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Environment: eclipse.buildId=4.10.0.I20181206-0815
> java.version=11.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
> Framework arguments: -product org.eclipse.epp.package.java.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
> Reporter: Emond Papegaaij
> Assignee: Jeff MAURY
> Priority: Major
> Labels: java_11
> Fix For: 4.11.0.Final
>
>
> When running Eclipse with Java 11, I keep getting the following error: An internal error occurred during: "Identify jrt-fs.jar". This happens when trying to open a class from the JRE in the editor. Looking at the stacktrace, this seems to originate from the JBoss Tools Maven Source Lookup. I'm using version 1.9.2.v20181211-1326.
> {code}
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (JBIDE-26571) Java 11: An internal error occurred during: "Identify jrt-fs.jar".
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26571?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-26571.
------------------------------
Resolution: Done
> Java 11: An internal error occurred during: "Identify jrt-fs.jar".
> ------------------------------------------------------------------
>
> Key: JBIDE-26571
> URL: https://issues.jboss.org/browse/JBIDE-26571
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Environment: eclipse.buildId=4.10.0.I20181206-0815
> java.version=11.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
> Framework arguments: -product org.eclipse.epp.package.java.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
> Reporter: Emond Papegaaij
> Assignee: Jeff MAURY
> Priority: Major
> Labels: java_11
> Fix For: 4.11.0.Final
>
>
> When running Eclipse with Java 11, I keep getting the following error: An internal error occurred during: "Identify jrt-fs.jar". This happens when trying to open a class from the JRE in the editor. Looking at the stacktrace, this seems to originate from the JBoss Tools Maven Source Lookup. I'm using version 1.9.2.v20181211-1326.
> {code}
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (JBIDE-26571) Java 11: An internal error occurred during: "Identify jrt-fs.jar".
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26571?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-26571:
----------------------------------
Resolution: (was: Done)
Assignee: Jeff MAURY
> Java 11: An internal error occurred during: "Identify jrt-fs.jar".
> ------------------------------------------------------------------
>
> Key: JBIDE-26571
> URL: https://issues.jboss.org/browse/JBIDE-26571
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Environment: eclipse.buildId=4.10.0.I20181206-0815
> java.version=11.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
> Framework arguments: -product org.eclipse.epp.package.java.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
> Reporter: Emond Papegaaij
> Assignee: Jeff MAURY
> Priority: Major
> Labels: java_11
>
> When running Eclipse with Java 11, I keep getting the following error: An internal error occurred during: "Identify jrt-fs.jar". This happens when trying to open a class from the JRE in the editor. Looking at the stacktrace, this seems to originate from the JBoss Tools Maven Source Lookup. I'm using version 1.9.2.v20181211-1326.
> {code}
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (ERT-718) [Wayland] Eclipse crashes after interaction with WebKit [EBZ#545275]
by Friendly Jira Robot (Jira)
Friendly Jira Robot created ERT-718:
---------------------------------------
Summary: [Wayland] Eclipse crashes after interaction with WebKit [EBZ#545275]
Key: ERT-718
URL: https://issues.jboss.org/browse/ERT-718
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
Using Eclipse SDK (master) from http://eclipse.matbooth.co.uk/flatpak/ .
Version: 2019-03 (4.11)
Build id: I20190211-1800
1) Start Eclipse in a new workspace
2) Create a new Java project
3) Open the type hierarchy (ctrl+shift+t) and open java.lang.Object
4) Hover over the Object type defintion (or anything that might display hover info with some data)
5) Once the hover gets focus (ie. doesn't disappear), start double clicking quickly, while continuing to move the mouse some small distance within the bounds of the hover.
Step 5 usually, though not consistently results in a crash.
C [libwayland-client.so.0+0x82a4] wl_proxy_get_user_data+0x4
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J 2507 org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(JZ)Z (0 bytes) @ 0x00007f831c574e84 [0x00007f831c574e40+0x0000000000000044]
J 11155 c2 org.eclipse.swt.widgets.Display.readAndDispatch()Z (77 bytes) @ 0x00007f831c61b220 [0x00007f831c61af80+0x00000000000002a0]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months