May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3909) rebrand dev platform installer as Red Hat Development Suite

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3909?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3909: ------------------------------------- [~sjcox] Could you update ,svg today? > rebrand dev platform installer as Red Hat Development Suite > ----------------------------------------------------------- > > Key: JBDS-3909 > URL: https://issues.jboss.org/browse/JBDS-3909 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Per decision made last week in https://trello.com/c/Cbo0q8TT/99-rebrand-jbds-as-rhds-using-rhd-logo and https://docs.google.com/presentation/d/1Ub-egAS7nbzFijKCTnUk7GJP8WPCQC28q... we need to refactor the platform installer to be the Development Suite installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3905) Add JSDT/Equinox hook for Nashorn to devstudio product configuration

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-3905?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-3905: ----------------------------------- [~akazakov] this is what I meant ;-) work = validation, content assist of new keywords, no false errors etc. > Add JSDT/Equinox hook for Nashorn to devstudio product configuration > -------------------------------------------------------------------- > > Key: JBDS-3905 > URL: https://issues.jboss.org/browse/JBDS-3905 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: build, javascript > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > We should add -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension to the devstudio product configuration to have JSDT working OOTB. > See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-222) Using Docker Daemon Registry (Default) may result in failure to authenticate [EBZ#494776]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-222?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg reassigned ERT-222: ----------------------------------- Assignee: Roland Grunberg > Using Docker Daemon Registry (Default) may result in failure to authenticate [EBZ#494776] > ----------------------------------------------------------------------------------------- > > Key: ERT-222 > URL: https://issues.jboss.org/browse/ERT-222 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > > For now the expectation should be that "Docker Daemon Registry (Default)" is accessing the default configured registry with no authentication credentials. > We still have : > try { > builder.authConfig(AuthConfig.fromDockerConfig().build()); > } catch (Exception e) { > // AuthConfig can't be found, continue > } > in the DockerClientFactory as part of the standard docker client creation. If the user actually has a config.json file in one of the searched locations, it'll be used. I think for now we should not support this because it's not really clear for the user that we're attempting to authenticate for them. We don't even restrict the auth credentials to jusy those matching the server name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-222) Using Docker Daemon Registry (Default) may result in failure to authenticate [EBZ#494776]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-222?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-222: -------------------------------- Sprint: devex #115 May 2016 > Using Docker Daemon Registry (Default) may result in failure to authenticate [EBZ#494776] > ----------------------------------------------------------------------------------------- > > Key: ERT-222 > URL: https://issues.jboss.org/browse/ERT-222 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > For now the expectation should be that "Docker Daemon Registry (Default)" is accessing the default configured registry with no authentication credentials. > We still have : > try { > builder.authConfig(AuthConfig.fromDockerConfig().build()); > } catch (Exception e) { > // AuthConfig can't be found, continue > } > in the DockerClientFactory as part of the standard docker client creation. If the user actually has a config.json file in one of the searched locations, it'll be used. I think for now we should not support this because it's not really clear for the user that we're attempting to authenticate for them. We don't even restrict the auth credentials to jusy those matching the server name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3905) Add JSDT/Equinox hook for Nashorn to devstudio product configuration

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3905?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3905: -------------------------------------- "editor works" can mean anything :) JS editor should provide, for example, validation. And there should not be errors in the log. > Add JSDT/Equinox hook for Nashorn to devstudio product configuration > -------------------------------------------------------------------- > > Key: JBDS-3905 > URL: https://issues.jboss.org/browse/JBDS-3905 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: build, javascript > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > We should add -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension to the devstudio product configuration to have JSDT working OOTB. > See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3905) Add JSDT/Equinox hook for Nashorn to devstudio product configuration

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-3905?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-3905: ----------------------------------- [~akazakov], [~nickboldt] ok I will do it. I guess the only way to test it is build studio against this PR and see if JSDT editor works > Add JSDT/Equinox hook for Nashorn to devstudio product configuration > -------------------------------------------------------------------- > > Key: JBDS-3905 > URL: https://issues.jboss.org/browse/JBDS-3905 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: build, javascript > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > We should add -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension to the devstudio product configuration to have JSDT working OOTB. > See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3905) Add JSDT/Equinox hook for Nashorn to devstudio product configuration

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3905?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3905: ------------------------------------ Assignee: Ilya Buziuk (was: Nick Boldt) The PR looks good but we should test it. [~ibuziuk], [~vrubezhny] could you yous guys test the PR and add steps to verify for QE. Thanks. > Add JSDT/Equinox hook for Nashorn to devstudio product configuration > -------------------------------------------------------------------- > > Key: JBDS-3905 > URL: https://issues.jboss.org/browse/JBDS-3905 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: build, javascript > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > We should add -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension to the devstudio product configuration to have JSDT working OOTB. > See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3905) Add JSDT/Equinox hook for Nashorn to devstudio product configuration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3905?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3905 at 5/27/16 1:41 PM: ----------------------------------------------------------- I've no idea how to test if this is working or not. https://github.com/jbdevstudio/jbdevstudio-product/pull/380 [~ibuziuk] [~vrubezhny] [~akazakov] can you confirm this is the fix you want? was (Author: nickboldt): I've no idea how to test if this is working or not. https://github.com/jbdevstudio/jbdevstudio-product/pull/380 > Add JSDT/Equinox hook for Nashorn to devstudio product configuration > -------------------------------------------------------------------- > > Key: JBDS-3905 > URL: https://issues.jboss.org/browse/JBDS-3905 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: build, javascript > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > We should add -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension to the devstudio product configuration to have JSDT working OOTB. > See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-703) JBDS-IS 9.0.0.GA is not listed in Red Hat marketplace

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-703?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-703: ----------------------------- Attachment: em1.png > JBDS-IS 9.0.0.GA is not listed in Red Hat marketplace > ----------------------------------------------------- > > Key: JBTIS-703 > URL: https://issues.jboss.org/browse/JBTIS-703 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Environment: Eclipse Mars.2 for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: em1.png > > > JBDS-IS 9.0.0.GA is not listed in Red Hat marketplace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-703) JBDS-IS 9.0.0.GA is not listed in Red Hat marketplace

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-703?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-703: ---------------------------------- [~nickboldt] - Hey Nick - do you know how one adds/ updates content to the Red Hat Eclipse Marketplaces client? > JBDS-IS 9.0.0.GA is not listed in Red Hat marketplace > ----------------------------------------------------- > > Key: JBTIS-703 > URL: https://issues.jboss.org/browse/JBTIS-703 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Environment: Eclipse Mars.2 for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > JBDS-IS 9.0.0.GA is not listed in Red Hat marketplace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016