September 2018 - jbosstools-issues

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Description: Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. was: Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Description: Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. was: Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4730: -------------------------------- Assignee: James Cobb (was: Nick Boldt) > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- 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 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) (?) Detect method references in comments (annotations) (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() ) 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 (eg. this is supported by existing indexer) (?) Detect method references in comments (annotations) (eg. 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() ) > 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 > (/) 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) > (?) Detect method references in comments (annotations) (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() ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Fix Version/s: 12.10.0.AM1 (was: 12.x) > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Description: Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ was: Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4730: -------------------------------- Summary: Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text Key: JBDS-4730 URL: https://issues.jboss.org/browse/JBDS-4730 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: build, installer Affects Versions: 12.0.0.AM1 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 12.0.0.GA Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- 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 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 (eg. this is supported by existing indexer) (?) Detect method references in comments (annotations) (eg. 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() ) 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 (?) 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() ) > 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 > (/) Basic performance test with just a JVM target platform, and lookup of java.lang.Object.toString() > (?) Detect method references even in dead code (eg. this is supported by existing indexer) > (?) Detect method references in comments (annotations) (eg. 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() ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Affects Version/s: 12.9.0.AM3 (was: 12.0.0.AM1) > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.x > > > Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Fix Version/s: 12.x (was: 12.0.0.GA) > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.x > > > Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- 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