December 2017 - jbosstools-issues

[JBoss JIRA] (ERT-570) Investigate/start work on menu popup issues

by Eric Williams (JIRA)

Eric Williams created ERT-570: --------------------------------- Summary: Investigate/start work on menu popup issues Key: ERT-570 URL: https://issues.jboss.org/browse/ERT-570 Project: Eclipse Release Train Issue Type: Task Reporter: Eric Williams Assignee: Eric Williams -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-569) Investigate/learn about DBus for Equinox launcher on Wayland

by Eric Williams (JIRA)

Eric Williams created ERT-569: --------------------------------- Summary: Investigate/learn about DBus for Equinox launcher on Wayland Key: ERT-569 URL: https://issues.jboss.org/browse/ERT-569 Project: Eclipse Release Train Issue Type: Task Reporter: Eric Williams Assignee: Eric Williams -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-552) Bug 525763: [GTK3] [dark theme] Vertical bar to the left of line numbers is not dark

by Eric Williams (JIRA)

[ https://issues.jboss.org/browse/ERT-552?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-552. ------------------------------- Resolution: Done > Bug 525763: [GTK3] [dark theme] Vertical bar to the left of line numbers is not dark > ------------------------------------------------------------------------------------ > > Key: ERT-552 > URL: https://issues.jboss.org/browse/ERT-552 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Eric Williams > Assignee: Eric Williams > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-568) [JDT] New API for organize imports

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-568?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg edited comment on ERT-568 at 12/14/17 11:43 AM: ---------------------------------------------------------------- I've proposed some changes for this, and improved them to reduce amount that is being exposed as API. The downside is there's quite a bit of code that has had to be copied over into internal spots of OrganizeImportsOperation. Trickiest spots have mainly been de-coupling OrganizeImportsOperation from JDT UI : * Dependence on JDT UI Plugin for the workspace preferences with respect to how imports are organized. The preference lookup is really part of org.eclipse.core.runtime so moving some code around handled this (eg. JavaUIPlugin.getInstance().getPreferences() vs. InstanceScope.getNode(..).get(..)) * Code depended on global ASTProvider stored in the JavaUIPlugin which hooked into various UI events (eg. editor opened/close). Resolved by moving all non-UI code into a new CoreASTProvider. This handles all calls that would have gone from SharedASTProvider -> ASTProvider * StringMatcher is used in so many spots across Eclipse ecosystem, and exposing it is no-go, so we use some crappy approximation using java.util.regex. I still need to confirm that taking this implementation will work for org.eclipse.jdt.ls, as their implementation may have hard-coded various things to work their way, while this proposed upstream implementation attempts to preserve how things worked in the JDT originally. was (Author: rgrunber): I've proposed some changes for this, and improved them to reduce amount that is being exposed as API. The downside is there's quite a bit of code that has had to be copied over into internal spots of OrganizeImportsOperation. Trickiest spots have been de-coupling OrganizeImportsOperation from JDT UI. Two cases existed : * Dependence on JDT UI Plugin for the workspace preferences with respect to how imports are organized. The preference lookup is really part of org.eclipse.core.runtime so moving some code around handled this (eg. JavaUIPlugin.getInstance().getPreferences() vs. InstanceScope.getNode(..).get(..)) * Code depended on global ASTProvider stored in the JavaUIPlugin which hooked into various UI events (eg. editor opened/close). Resolved by moving all non-UI code into a new CoreASTProvider. This handles all calls that would have gone from SharedASTProvider -> ASTProvider I still need to confirm that taking this implementation will work for org.eclipse.jdt.ls, as their implementation may have hard-coded various things to work their way, while this proposed upstream implementation attempts to preserve how things worked in the JDT originally. > [JDT] New API for organize imports > ---------------------------------- > > Key: ERT-568 > URL: https://issues.jboss.org/browse/ERT-568 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=506239 for full details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-568) [JDT] New API for organize imports

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-568?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg edited comment on ERT-568 at 12/14/17 11:37 AM: ---------------------------------------------------------------- I've proposed some changes for this, and improved them to reduce amount that is being exposed as API. The downside is there's quite a bit of code that has had to be copied over into internal spots of OrganizeImportsOperation. Trickiest spots have been de-coupling OrganizeImportsOperation from JDT UI. Two cases existed : * Dependence on JDT UI Plugin for the workspace preferences with respect to how imports are organized. The preference lookup is really part of org.eclipse.core.runtime so moving some code around handled this (eg. JavaUIPlugin.getInstance().getPreferences() vs. InstanceScope.getNode(..).get(..)) * Code depended on global ASTProvider stored in the JavaUIPlugin which hooked into various UI events (eg. editor opened/close). Resolved by moving all non-UI code into a new CoreASTProvider. This handles all calls that would have gone from SharedASTProvider -> ASTProvider I still need to confirm that taking this implementation will work for org.eclipse.jdt.ls, as their implementation may have hard-coded various things to work their way, while this proposed upstream implementation attempts to preserve how things worked in the JDT originally. was (Author: rgrunber): I've proposed some changes for this, and improved them to reduce amount that is being exposed as API. The downside is there's quite a bit of code that has had to be copied over into internal spots of OrganizeImportsOperation. I still need to confirm that taking this implementation will work for org.eclipse.jdt.ls, but from an upstream point of view this provides OrganizeImportsOperation as API. > [JDT] New API for organize imports > ---------------------------------- > > Key: ERT-568 > URL: https://issues.jboss.org/browse/ERT-568 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=506239 for full details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24897: ------------------------------------ http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > Attachments: fabric8-connector.png > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24897: ------------------------------------ Where can I download latest because I can't build it anymore on Windows and I remember I add some issues on Windows and want to double check ? > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > Attachments: fabric8-connector.png > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-568) [JDT] New API for organize imports

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-568?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-568: ------------------------------------- I've proposed some changes for this, and improved them to reduce amount that is being exposed as API. The downside is there's quite a bit of code that has had to be copied over into internal spots of OrganizeImportsOperation. I still need to confirm that taking this implementation will work for org.eclipse.jdt.ls, but from an upstream point of view this provides OrganizeImportsOperation as API. > [JDT] New API for organize imports > ---------------------------------- > > Key: ERT-568 > URL: https://issues.jboss.org/browse/ERT-568 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=506239 for full details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-568) New API for organize imports

by Roland Grunberg (JIRA)

Roland Grunberg created ERT-568: ----------------------------------- Summary: New API for organize imports Key: ERT-568 URL: https://issues.jboss.org/browse/ERT-568 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Roland Grunberg Assignee: Roland Grunberg See https://bugs.eclipse.org/bugs/show_bug.cgi?id=506239 for full details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-568) New API for organize imports

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-568?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-568: -------------------------------- Sprint: devex #142 December 2017 > New API for organize imports > ---------------------------- > > Key: ERT-568 > URL: https://issues.jboss.org/browse/ERT-568 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=506239 for full details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017