[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 (was: devex #155 September 2018, devex #156 October 2018)
> 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
[JBoss JIRA] (ERT-647) Resolve remaining issues with Batik 1.9.1
by Sopot Cela (Jira)
[ https://issues.jboss.org/browse/ERT-647?page=com.atlassian.jira.plugin.sy... ]
Sopot Cela updated ERT-647:
---------------------------
Sprint: devex #152 July 2018, devex #153 August 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019 (was: devex #152 July 2018, devex #153 August 2018, devex #155 September 2018, devex #156 October 2018)
> Resolve remaining issues with Batik 1.9.1
> -----------------------------------------
>
> Key: ERT-647
> URL: https://issues.jboss.org/browse/ERT-647
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
> Priority: Major
>
> Batik 1.9.1 had some remaining issues that prevented the full stack from being adopted during the Photon release train by some other projects (eg. Sirius, Papyrus, GMF, BIRT, Graphiti, etc.)
> We should resolve the remaining issues, re-include all the bundles in the stack and finally upgrade to Batik 1.10.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (ERT-656) Cannot run JUnit test method having parameter
by Sopot Cela (Jira)
[ https://issues.jboss.org/browse/ERT-656?page=com.atlassian.jira.plugin.sy... ]
Sopot Cela updated ERT-656:
---------------------------
Sprint: devex #153 August 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019 (was: devex #153 August 2018, devex #155 September 2018, devex #156 October 2018)
> Cannot run JUnit test method having parameter
> ---------------------------------------------
>
> Key: ERT-656
> URL: https://issues.jboss.org/browse/ERT-656
> Project: Eclipse Release Train
> Issue Type: Task
> Affects Versions: Oxygen.1 (4.7), Photon (4.8), 2018-09 M2
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
> Priority: Major
>
> Since Oxygen.0, some changes introduced for JUnit 5 support, regressed the ability to run individual test methods that happen to take a parameter (eg. testFoo(TestContext) ). The filter matching against the method itself was broken.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (ERT-677) Fix some small bugs in JDT
by Sopot Cela (Jira)
[ https://issues.jboss.org/browse/ERT-677?page=com.atlassian.jira.plugin.sy... ]
Sopot Cela updated ERT-677:
---------------------------
Sprint: devex #156 October 2018, devex #157 November 2019 (was: devex #156 October 2018)
> Fix some small bugs in JDT
> --------------------------
>
> Key: ERT-677
> URL: https://issues.jboss.org/browse/ERT-677
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
> Priority: Major
>
> (/) Bug 517297 - NewContainerWizardPage.getInitialJavaElement() returns IJavaElement for non-Java project
> (/) Bug 538236 - Alphabetically sort of libraries also sorts source folder
> (/) Bug 539289: [10] Quick fix "Surround with try/catch" generates invalid code with java 10 var
> (/) Bug 514054: [1.9] Introduce new context for code templates for module-info.java
> (/) Bug 536058: [JUnit 5] TestRunListenerTest5 fails when JUnit plug-ins are imported in workspace
> (?) Bug 526339: [9][quick fix] should propose to add a "provider method"
> (?) Bug 525632: [JUnit][quick assist] Offer Quick Assists for the creation of a JUnit test
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26435) Hibernate JPA Model Generator and Java 11
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26435?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26435:
-------------------------------
Fix Version/s: 4.10.x
> Hibernate JPA Model Generator and Java 11
> -----------------------------------------
>
> Key: JBIDE-26435
> URL: https://issues.jboss.org/browse/JBIDE-26435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.9.0.Final
> Reporter: Cody Lerum
> Priority: Major
> Fix For: 4.10.x
>
> Attachments: screenshot-1.png
>
>
> Not sure if this ends up being related to Jboss tools or just the Eclipse JDT
> But on 2018-09 with 4.9.Final a project cannot be cleanly built using the org.hibernate:hibernate-jpamodelgen
> Everything builds and then at the end it seems to delete the generated sources.
> This only occurs it the Java 11 support plugin is installed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4735:
-----------------------------
Fix Version/s: 12.10.0.AM1
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 12.9.0.GA
> Environment: manually Fedora 28, automation
> Reporter: Vojtech Prusa
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.10.0.AM1
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png
>
>
> Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached).
> Nothing in Error log view.
> Restarting devstudio solves the issue.
> Adding screen and central tar of:
> devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years