October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-652) Eclipse Platform core maintenance

by Sopot Cela (Jira)

[ https://issues.jboss.org/browse/ERT-652?page=com.atlassian.jira.plugin.sy... ] Sopot Cela updated ERT-652: --------------------------- 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) > Eclipse Platform core maintenance > --------------------------------- > > Key: ERT-652 > URL: https://issues.jboss.org/browse/ERT-652 > Project: Eclipse Release Train > Issue Type: Bug > Reporter: Sopot Cela > Assignee: Alexander Kurtakov > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-26384) Add "jboss-web_12_1.xsd" and others

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26384?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26384: ------------------------------- Fix Version/s: 4.10.0.AM1 > Add "jboss-web_12_1.xsd" and others > ----------------------------------- > > Key: JBIDE-26384 > URL: https://issues.jboss.org/browse/JBIDE-26384 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.Final > Reporter: Wolfgang Knauf > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.10.0.AM1 > > > Recently, a bunch of new XSD files were added that should be added to XML catalog: > jboss-web_11_1.xsd, jboss-web_12_1.xsd, jboss-web_13_0.xsd, which include jboss-common_7_1.xsd, jboss-common_8_0.xsd > Note that the schema location of those files files has changed compared to previous files, e.g. http://www.jboss.org/schema/jbossas/jboss-web_12_1.xsd or http://www.jboss.org/schema/jbossas/jboss-common_7_1.xsd > Do you pull most recent versions of those files from Git automatically when creating the a new JBoss Tools release? Recently, some typos in older XML files were fixed, and the new files seem to undergo some changes, so it would probably bad to pull a "work in progress" file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBTIS-1240) JBTIS TP refers update site which doesn't exist

by Paul Leacu (Jira)

[ https://issues.jboss.org/browse/JBTIS-1240?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1240: ----------------------------------- Cool - I'll fix this when we resync up with the JBT TP - probably next month > JBTIS TP refers update site which doesn't exist > ----------------------------------------------- > > Key: JBTIS-1240 > URL: https://issues.jboss.org/browse/JBTIS-1240 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.6.0.Final > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Major > > {code} > [ERROR] Failed to resolve target definition /home/fedora/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.6.1.Final-SNAPSHOT/target-platform-4.6.1.Final-SNAPSHOT-base.target: Failed to load p2 metadata repository from location http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6...: No repository found at http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6.... -> [Help 1] > {code} > The same applies for JBTIS TP 4.6.0.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1240) JBTIS TP refers update site which doesn't exist

by Andrej Podhradsky (Jira)

[ https://issues.jboss.org/browse/JBTIS-1240?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1240: ------------------------------------- Priority: Major (was: Blocker) > JBTIS TP refers update site which doesn't exist > ----------------------------------------------- > > Key: JBTIS-1240 > URL: https://issues.jboss.org/browse/JBTIS-1240 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.6.0.Final > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Major > > {code} > [ERROR] Failed to resolve target definition /home/fedora/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.6.1.Final-SNAPSHOT/target-platform-4.6.1.Final-SNAPSHOT-base.target: Failed to load p2 metadata repository from location http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6...: No repository found at http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6.... -> [Help 1] > {code} > The same applies for JBTIS TP 4.6.0.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1240) JBTIS TP refers update site which doesn't exist

by Andrej Podhradsky (Jira)

[ https://issues.jboss.org/browse/JBTIS-1240?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1240: ------------------------------------------ Hi [~pleacu], you are right, this is not a blocker. I have already lowered the priority. > JBTIS TP refers update site which doesn't exist > ----------------------------------------------- > > Key: JBTIS-1240 > URL: https://issues.jboss.org/browse/JBTIS-1240 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.6.0.Final > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Major > > {code} > [ERROR] Failed to resolve target definition /home/fedora/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.6.1.Final-SNAPSHOT/target-platform-4.6.1.Final-SNAPSHOT-base.target: Failed to load p2 metadata repository from location http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6...: No repository found at http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6.... -> [Help 1] > {code} > The same applies for JBTIS TP 4.6.0.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1240) JBTIS TP refers update site which doesn't exist

by Paul Leacu (Jira)

[ https://issues.jboss.org/browse/JBTIS-1240?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1240: ----------------------------------- Hey [~apodhrad] - the issue is just that this line should have been commented out: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... Is this really a blocker? It shouldn't have affected the product at all (the next line defined the stable URL to fine coretests). > JBTIS TP refers update site which doesn't exist > ----------------------------------------------- > > Key: JBTIS-1240 > URL: https://issues.jboss.org/browse/JBTIS-1240 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.6.0.Final > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > {code} > [ERROR] Failed to resolve target definition /home/fedora/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.6.1.Final-SNAPSHOT/target-platform-4.6.1.Final-SNAPSHOT-base.target: Failed to load p2 metadata repository from location http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6...: No repository found at http://download.jboss.org/jbosstools/photon/staging/updates/coretests/4.6.... -> [Help 1] > {code} > The same applies for JBTIS TP 4.6.0.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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 October 2018