[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26388:
-------------------------------
Attachment: (was: 4.10.0.AM1.M1-4.10.0.AM1.M2.p2diff.txt)
> TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)
> -----------------------------------------------------------------
>
> Key: JBIDE-26388
> URL: https://issues.jboss.org/browse/JBIDE-26388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.10.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Major
> Labels: releasework
> Fix For: 4.10.0.AM1, 4.10.0.Final
>
> Attachments: jbosstools-multiple-considerversions-4.9.0.Final-4.10.0.AM1.p2diff, jbosstools-multiple-ignoreversions-4.9.0.Final-4.10.0.AM1.p2diff
>
>
> In order to start Eclipse 4.10-based builds, we need an updated target platform.
> Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit!
> For sprint 156 / AM1: simrel M1
> For sprint 157 / AM1: simrel M2
> For sprint 158 / GA: simrel M3/RC1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBIDE-26463) Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin)
by Bob Davis (Jira)
[ https://issues.jboss.org/browse/JBIDE-26463?page=com.atlassian.jira.plugi... ]
Bob Davis commented on JBIDE-26463:
-----------------------------------
Assuming that there are no technical details to hammer out, we need to make sure that:
* The name is the same as what we're calling it in the VS Code Marketplace
* In the same lines as that, the publisher should be "Red Hat"
* Any icons need to be the same as what we have done in the VS Code Marketplace
This is to ensure that anyone looking at these will quickly see that the are the same thing.
If the names/logos are not the same for DevStudio, we should address that as well and update them.
Bob
> Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin)
> --------------------------------------------------------------------------
>
> Key: JBIDE-26463
> URL: https://issues.jboss.org/browse/JBIDE-26463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace, updatesite
> Affects Versions: 4.10.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Major
>
> Per discussion w/ [~mickael_istria] [~rpdavis] and [~jeffmaury], we should create a new Eclipse Marketplace entry for the fabric8 analytics plugin.
> This will require that the plugin & feature have its own dedicated update site, unless we plan to just point the entry at the latest devstudio or jbosstools site.
> Will also need to determine how to describe the plugin, provide an icon and/or screenshot, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBIDE-26463) Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin)
by Mickael Istria (Jira)
[ https://issues.jboss.org/browse/JBIDE-26463?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-26463:
----------------------------------------
Is there anything preventing from creating the Marketplace entry already? The feature name and other technical details don't have much impact on that work and are not blockers AFAIK.
> Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin)
> --------------------------------------------------------------------------
>
> Key: JBIDE-26463
> URL: https://issues.jboss.org/browse/JBIDE-26463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace, updatesite
> Affects Versions: 4.10.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Major
>
> Per discussion w/ [~mickael_istria] [~rpdavis] and [~jeffmaury], we should create a new Eclipse Marketplace entry for the fabric8 analytics plugin.
> This will require that the plugin & feature have its own dedicated update site, unless we plan to just point the entry at the latest devstudio or jbosstools site.
> Will also need to determine how to describe the plugin, provide an icon and/or screenshot, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBDS-4746) GPG key for code siging
by Mat Booth (Jira)
[ https://issues.jboss.org/browse/JBDS-4746?page=com.atlassian.jira.plugin.... ]
Mat Booth updated JBDS-4746:
----------------------------
Description:
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 ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring.
was:
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, there was no such keyring.
> GPG key for code siging
> -----------------------
>
> Key: JBDS-4746
> URL: https://issues.jboss.org/browse/JBDS-4746
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> 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 ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBDS-4746) GPG key for code siging
by Mat Booth (Jira)
[ https://issues.jboss.org/browse/JBDS-4746?page=com.atlassian.jira.plugin.... ]
Mat Booth updated JBDS-4746:
----------------------------
Description:
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.
was:
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 ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring.
> GPG key for code siging
> -----------------------
>
> Key: JBDS-4746
> URL: https://issues.jboss.org/browse/JBDS-4746
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> 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)
7 years, 4 months
[JBoss JIRA] (JBDS-4746) GPG key for code siging
by Mat Booth (Jira)
[ https://issues.jboss.org/browse/JBDS-4746?page=com.atlassian.jira.plugin.... ]
Mat Booth commented on JBDS-4746:
---------------------------------
I assigned this straight to Ondrej since he took an interest in Flatpak last time I needed something, hope that's okay :-)
> GPG key for code siging
> -----------------------
>
> Key: JBDS-4746
> URL: https://issues.jboss.org/browse/JBDS-4746
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> 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, there was no such keyring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBDS-4746) GPG key for code siging
by Mat Booth (Jira)
[ https://issues.jboss.org/browse/JBDS-4746?page=com.atlassian.jira.plugin.... ]
Mat Booth reassigned JBDS-4746:
-------------------------------
Assignee: Ondrej Dockal
> GPG key for code siging
> -----------------------
>
> Key: JBDS-4746
> URL: https://issues.jboss.org/browse/JBDS-4746
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> 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, there was no such keyring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBDS-4746) GPG key for code siging
by Mat Booth (Jira)
Mat Booth created JBDS-4746:
-------------------------------
Summary: GPG key for code siging
Key: JBDS-4746
URL: https://issues.jboss.org/browse/JBDS-4746
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: build
Reporter: Mat Booth
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, there was no such keyring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26388:
---------------------------------------
[~jeffmaury] Thanks Jeff!
> TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)
> -----------------------------------------------------------------
>
> Key: JBIDE-26388
> URL: https://issues.jboss.org/browse/JBIDE-26388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.10.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Major
> Labels: releasework
> Fix For: 4.10.0.AM1, 4.10.0.Final
>
> Attachments: 4.10.0.AM1.M1-4.10.0.AM1.M2.p2diff.txt, jbosstools-multiple-considerversions-4.9.0.Final-4.10.0.AM1.p2diff, jbosstools-multiple-ignoreversions-4.9.0.Final-4.10.0.AM1.p2diff
>
>
> In order to start Eclipse 4.10-based builds, we need an updated target platform.
> Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit!
> For sprint 156 / AM1: simrel M1
> For sprint 157 / AM1: simrel M2
> For sprint 158 / GA: simrel M3/RC1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months