October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26436) Add WF14 in ITest suite

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26436?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26436: ---------------------------------- Fix Version/s: 4.10.0.AM1 > Add WF14 in ITest suite > ----------------------- > > Key: JBIDE-26436 > URL: https://issues.jboss.org/browse/JBIDE-26436 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.10.0.AM1 > Environment: jenkins > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > > Add WF 14 in ITest suite for testing server -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26436) Add WF14 in ITest suite

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26436?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26436. --------------------------------- Resolution: Done > Add WF14 in ITest suite > ----------------------- > > Key: JBIDE-26436 > URL: https://issues.jboss.org/browse/JBIDE-26436 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.10.0.AM1 > Environment: jenkins > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > > Add WF 14 in ITest suite for testing server -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-647) Resolve remaining issues with Batik 1.9.1

by Roland Grunberg (Jira)

[ https://issues.jboss.org/browse/ERT-647?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-647: ------------------------------------- I have received confirmation that my proposed fixes would make Batik 1.9.1 usable by BIRT from committers on the project. Need to hear back with respect to whether lack of full 1.10 stack is a no-go for them, or whether they'd be willing to accept 1.9.1. > 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, 5 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 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 (/) 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 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. (/) 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 > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26416) AM3 download pages missing update site URLs

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26416?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-26416. -------------------------------- Resolution: Done Fixed. Problem was we'd forgotten to add the URLs for am2 and am3: https://github.com/jbosstools/jbosstools-website/commit/61df7f1ec8239c3df... Also forgot to add the URL for 4.9.0.Final: https://github.com/jbosstools/jbosstools-website/commit/ae7c8cb440640c4f4... And I archived 4.6.0.AM3: https://github.com/jbosstools/jbosstools-website/commit/59f38684f50edc555... > AM3 download pages missing update site URLs > ------------------------------------------- > > Key: JBIDE-26416 > URL: https://issues.jboss.org/browse/JBIDE-26416 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Rob Stryker > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.10.0.AM1 > > > See http://tools.jboss.org/downloads/jbosstools/2018-09/4.9.0.AM3.html > Note that there is no update site URL. > See http://tools.jboss.org/downloads/jbosstools/2018-09/4.9.x.Nightly.html > Note that an update site URL *is* present. > TODO: fix am3.html to include a link to the update site > TODO: make sure 4.9.0.Final (when released) also has a linked update site. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4710: ----------------------------- Attachment: screenshot-1.png > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.x > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png, screenshot-1.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Jeff MAURY edited comment on JBDS-4710 at 10/11/18 8:14 AM: ------------------------------------------------------------ Tested with 12.9.0.GA on F27 and got crash in webkitgtk4. See !screenshot-1.png|thumbnail! was (Author: jeffmaury): Tested with 12.9.0.GA on F27 and got crash in webkitgtk4 > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.x > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png, screenshot-1.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26441) The server was shutdown forcefully. All processes were terminated.

by Rakesh Jain (Jira)

Rakesh Jain created JBIDE-26441: ----------------------------------- Summary: The server was shutdown forcefully. All processes were terminated. Key: JBIDE-26441 URL: https://issues.jboss.org/browse/JBIDE-26441 Project: Tools (JBoss Tools) Issue Type: Bug Environment: eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 java.version=1.8.0_181 jboss data virtualization server 6.3 Reporter: Rakesh Jain eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 java.version=1.8.0_181 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product com.jboss.devstudio.core.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4710: ---------------------------------- Tested with 12.9.0.GA on F27 and got crash in webkitgtk4 > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.x > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[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 closed JBIDE-26435. ------------------------------ Resolution: Cannot Reproduce > 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 > 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, 5 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 October 2018