[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 (was: devex #155 September 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 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() )
> 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, 6 months
[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 (was: devex #152 July 2018, devex #153 August 2018, devex #155 September 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, 6 months
[JBoss JIRA] (JBIDE-26389) NPE while "Searching Runtimes"
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26389?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26389:
-------------------------------------
Fix Version/s: 4.10.0.AM1
> NPE while "Searching Runtimes"
> ------------------------------
>
> Key: JBIDE-26389
> URL: https://issues.jboss.org/browse/JBIDE-26389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.9.0.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> {code}
> eclipse.buildId=12.9.0.GA-v20180928-1629-B3448
> java.version=1.8.0_181
> 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: -data file:/home/odockal/workspace1290GA/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.core.jobs
> Error
> Sun Sep 30 20:56:59 CEST 2018
> An internal error occurred during: "Searching runtimes...".
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderWhiteListBin(UnifiedMinishiftRuntimeDetector.java:150)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.getMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:139)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderContainsMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:144)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.minishiftHomeMatches(UnifiedMinishiftRuntimeDetector.java:180)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.matches(UnifiedMinishiftRuntimeDetector.java:171)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.AbstractCDKRuntimeDetector.exists(AbstractCDKRuntimeDetector.java:111)
> at org.jboss.tools.runtime.core.internal.RuntimeDetector.exists(RuntimeDetector.java:68)
> at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:131)
> at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:122)
> at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:118)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.wouldOpenSearchRuntimePathDialog(RuntimeScanner.java:152)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.access$0(RuntimeScanner.java:129)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:81)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBTIS-1239) Cannot install Devstudio IS 12.0.0.GA into Devstudio 12.9.0.GA in offline mode
by Paul Leacu (Jira)
[ https://issues.jboss.org/browse/JBTIS-1239?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1239:
---------------------------------
Assignee: Paul Leacu
> Cannot install Devstudio IS 12.0.0.GA into Devstudio 12.9.0.GA in offline mode
> ------------------------------------------------------------------------------
>
> Key: JBTIS-1239
> URL: https://issues.jboss.org/browse/JBTIS-1239
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Affects Versions: 12.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Major
>
> When installing Devstudio IS 12.0.0.GA into Devstudio 12.9.0.GA in offline mode, I'm getting the following error
> {code}
> !ENTRY org.eclipse.equinox.p2.director 4 10054 2018-10-04 07:10:12.964
> !MESSAGE Cannot complete the install because of a conflicting dependency.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.966
> !MESSAGE Software being installed: EMF - Eclipse Modeling Framework Core Runtime 2.14.0.v20180529-1144 (org.eclipse.emf.ecore.feature.group 2.14.0.v20180529-1144)
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.968
> !MESSAGE Software being installed: Teiid Designer 11.2.0.v20180723-1437 (org.teiid.designer.feature.feature.group 11.2.0.v20180723-1437)
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2018-10-04 07:10:12.971
> !MESSAGE Only one of the following can be installed at once:
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.974
> !MESSAGE EMF Ecore 2.14.0.v20180529-1144 (org.eclipse.emf.ecore 2.14.0.v20180529-1144)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.977
> !MESSAGE EMF Ecore 2.15.0.v20180722-1159 (org.eclipse.emf.ecore 2.15.0.v20180722-1159)
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2018-10-04 07:10:12.978
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.979
> !MESSAGE From: EMF - Eclipse Modeling Framework Core Runtime 2.14.0.v20180529-1144 (org.eclipse.emf.ecore.feature.group 2.14.0.v20180529-1144)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.980
> !MESSAGE To: org.eclipse.equinox.p2.iu; org.eclipse.emf.ecore [2.14.0.v20180529-1144,2.14.0.v20180529-1144]
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2018-10-04 07:10:12.981
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.982
> !MESSAGE From: EMF Mapping 2.11.0.v20180706-1146 (org.eclipse.emf.mapping 2.11.0.v20180706-1146)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.983
> !MESSAGE To: osgi.bundle; org.eclipse.emf.ecore [2.15.0,3.0.0)
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2018-10-04 07:10:12.985
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.986
> !MESSAGE From: Teiid Designer 11.2.0.v20180723-1437 (org.teiid.designer.feature.feature.group 11.2.0.v20180723-1437)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2018-10-04 07:10:12.989
> !MESSAGE To: org.eclipse.equinox.p2.iu; org.eclipse.emf.mapping [2.8.0,3.0.0)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months