[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] Hi, can we please update RedDeer to latest milestone as well: http://download.eclipse.org/reddeer/milestones/2.4.0.M2?
Thanks
> 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
[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 commented on JBIDE-26388:
------------------------------------
Updated TP with:
- 2018-12M2
- Jetty 9.4.13
- WTP S-3.12.0.M2-20181101035339
p2diff log is here: [^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: 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
[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: 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: 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
[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25586:
------------------------------------------
[~jkopriva] so this means that we cannot reproduce this in FC28, FC29?
> OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
> ----------------------------------------------------------------
>
> Key: JBIDE-25586
> URL: https://issues.jboss.org/browse/JBIDE-25586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Environment: FC27
> OpenJDK 9.0.1
> CDK v3.3.0-rc.1-1
> eclipse.buildId=11.2.0.GA-v20180115-0516-B1866
> java.version=9.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: cdk, connection
> Fix For: 4.9.0.Final
>
>
> But, connecting to online openshift instance works.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBIDE-25903) New wizards: pointless Help button
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-25903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25903:
------------------------------------------
It is very unlikely that we'll provide contextual help for the wizards in the OpenShift tooling for Eclipse. Setting fixVersion to LATER.
> New wizards: pointless Help button
> ----------------------------------
>
> Key: JBIDE-25903
> URL: https://issues.jboss.org/browse/JBIDE-25903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.5.3.Final
> Environment: F28
> Reporter: Josef Kopriva
> Priority: Minor
> Labels: ux
> Fix For: LATER
>
> Attachments: image-2018-04-05-08-19-09-880.png, new-resource-wizard.png
>
>
> !image-2018-04-05-08-19-09-880.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ERT-666) Improve JDT Indexer performance for method reference lookups
by Sopot Cela (Jira)
[ https://issues.jboss.org/browse/ERT-666?page=com.atlassian.jira.plugin.sy... ]
Sopot Cela updated ERT-666:
---------------------------
Sprint: devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2019 (was: devex #155 September 2018, devex #156 October 2018, devex #157 November 2019)
> Improve JDT Indexer performance for method reference lookups
> ------------------------------------------------------------
>
> Key: ERT-666
> URL: https://issues.jboss.org/browse/ERT-666
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
> Priority: Major
>
> Based on discussions with Igor, various proposals were made to improve the method reference lookup times of the JDT Indexer.
> One particular suggestion, which should be possible, with least amount of friction, would be to provide more information about the declaring type of a method in the indexer format.
> The methodRef category table currently stores :
> (symbol, number of arguments) -> document numbers (classfiles)
> toString/0 -> [1, 4, 5, 25]
> The proposal would change this to :
> (symbol, symbol's classname, classname) -> document numbers (classfiles)
> toString/0/java.lang.Object -> [1, 4, 5, 25]
> Doing so should reduce the number of post-processing changes needed to verify that the declaring type of the first set of matches corresponds to the declaring type of the selected reference.
> (/) Make the patch mostly correct
> (/) Basic performance test with just a JVM target platform, and lookup of java.lang.Object.toString()
> (?) Detect method references even in dead code (this is supported by existing indexer)
> (/) More complicated performance test against top 500 used JRE references
> (/) A more thorough correctness test to identify any additional differences. (eg. test every single possible method reference, not just toString() )
> Upstream Bug : https://bugs.eclipse.org/bugs/show_bug.cgi?id=539159
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months