September 2018 - jbosstools-issues

[JBoss JIRA] (ERT-666) Improve JDT Indexer performance for method reference lookups

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-666?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-666: -------------------------------- Description: 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 (?) Handle some more difficult corner cases (eg. detect references even to dead code) (/) Basic performance test with just a JVM target platform, and lookup of java.lang.Object.toString() (?) More complicated performance test against the Eclipse Platform itself for java.lang.Object.toString() (?) A more thorough correctness test to identify any additional differences. (eg. test every single possible method reference, not just toString() ) was: 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. > 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 > > 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 > (?) Handle some more difficult corner cases (eg. detect references even to dead code) > (/) Basic performance test with just a JVM target platform, and lookup of java.lang.Object.toString() > (?) More complicated performance test against the Eclipse Platform itself for java.lang.Object.toString() > (?) A more thorough correctness test to identify any additional differences. (eg. test every single possible method reference, not just toString() ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4728) Jboss Developer Studio Hangs on Step 8 of 10

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4728?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4728: ----------------------------- Sprint: devex #155 September 2018 > Jboss Developer Studio Hangs on Step 8 of 10 > -------------------------------------------- > > Key: JBDS-4728 > URL: https://issues.jboss.org/browse/JBDS-4728 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.0.0.GA > Environment: Windows 7 (Enterprise) 64bit > Reporter: Susmit Dey > Assignee: Nick Boldt > Fix For: 12.9.0.GA > > Attachments: JBDS_Hung.jpg > > > devstudio-12.0.0.GA-installer-standalone installer hangs on step 8 of 10 > installation progress stuck at 1/3 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26180: ------------------------------- Sprint: devex #152 July 2018, devex #153 August 2018, devex #155 September 2018 (was: devex #152 July 2018, devex #153 August 2018, devex #154 September 2018) > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt, p2diff.am2.am3.all.ignoreVersions.txt, p2diff.am2.am3.all.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA > Coming in the next update, some orbit changes: > * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) > Also: > * reddeer 2.3 > * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-666) Improve JDT Indexer performance for method reference lookups

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-666?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-666: ------------------------------------- The patch as it exists in current form seems to improve performance for method reference lookups significantly. > 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 > > 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. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26301) Reduce CVE issues in org.fusesource.ide bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26301: ------------------------------- Fix Version/s: 4.9.0.Final (was: 4.9.0.AM3) > Reduce CVE issues in org.fusesource.ide bundles > ----------------------------------------------- > > Key: JBIDE-26301 > URL: https://issues.jboss.org/browse/JBIDE-26301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.Final > > > Some CVE issues exist in fuse bundles: > {code:title=unpacked/devstudio-12.9.0.AM2-v20180808-0721-B3149-updatesite-core/} > org.fusesource.ide.camel.model.service.impl.v2151redhat621216_11.1.0.v20180723-1842.jar/libs > org.fusesource.ide.camel.model.service.impl.v2151redhat621216_11.1.0.v20180723-1842.jar/libs/camel-core-2.15.1.redhat-621216.jar/META-INF/maven/org.apache.camel/camel-core > org.fusesource.ide.camel.model.service.impl.v2170redhat630347_11.1.0.v20180725-0619.jar/libs > org.fusesource.ide.camel.model.service.impl.v2170redhat630347_11.1.0.v20180725-0619.jar/libs/camel-core-2.17.0.redhat-630347.jar/META-INF/maven/org.apache.camel/camel-core > org.fusesource.ide.camel.model.service.impl.v2181redhat000021_11.1.0.v20180723-1842.jar/libs > org.fusesource.ide.camel.model.service.impl.v2181redhat000021_11.1.0.v20180723-1842.jar/libs/camel-core-2.18.1.redhat-000021.jar/META-INF/maven/org.apache.camel/camel-core > org.fusesource.ide.camel.model.service.impl.v2181redhat000021_11.1.0.v20180723-1842.jar/libs/camel-core-2.18.1.redhat-000021.jar/META-INF/maven/org.apache.camel/spi-annotations > org.fusesource.ide.camel.model.service.impl.v2203_11.1.0.v20180723-1842.jar/libs > org.fusesource.ide.camel.model.service.impl.v2210fuse000077redhat1_11.1.0.v20180723-1842.jar/libs > org.fusesource.ide.camel.model.service.impl_11.1.0.v20180801-0947.jar/libs > org.fusesource.ide.jmx.activemq_11.1.0.v20180723-1842.jar/libs > org.fusesource.ide.wsdl2rest_11.1.0.v20180807-1302.jar/libs{code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Verification: check if we have fewer CVEs after updating to newer version of fuse 11.1.x: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103 > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26302) Reduce CVE issues in JBT seam bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26302?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26302: ------------------------------- Fix Version/s: 4.9.0.Final (was: 4.9.0.AM3) > Reduce CVE issues in JBT seam bundles > ------------------------------------- > > Key: JBIDE-26302 > URL: https://issues.jboss.org/browse/JBIDE-26302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.Final > > > Some CVE issues exist in seam bundles: > {code} > org.jboss.tools.cdi.seam.core_1.8.301.v20180807-1920.jar > org.jboss.tools.maven.seam_1.9.1.v20180802-1520.jar{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Verification: check if we have fewer CVEs after updating to newer version of fuse 11.1.x: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103 > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26283: ------------------------------- Sprint: devex #155 September 2018 (was: devex #154 September 2018) > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26345) Docker New and Noteworthy for 4.9.0.Final

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26345?page=com.atlassian.jira.plugi... ] Jeff Johnston closed JBIDE-26345. --------------------------------- Resolution: Rejected > Docker New and Noteworthy for 4.9.0.Final > ----------------------------------------------------- > > Key: JBIDE-26345 > URL: https://issues.jboss.org/browse/JBIDE-26345 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Labels: task > Fix For: 4.9.0.Final > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26340 #comment Create N&N for Docker 4.9.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Docker for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.9.0.Final since the AM3 release of Docker, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.9.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.9.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26283: ------------------------------------ Downgraded and set back to 4.9.0.Final to see what happens after we prepare for the Final release. > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26283: ------------------------------- Labels: releasework (was: ) > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2018