May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22456) DCP v1 API is phasing out, need to migrate to v2, ensure old JBDS versions will survive

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22456?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22456: ----------------------------------- Assignee: Fred Bricon > DCP v1 API is phasing out, need to migrate to v2, ensure old JBDS versions will survive > --------------------------------------------------------------------------------------- > > Key: JBIDE-22456 > URL: https://issues.jboss.org/browse/JBIDE-22456 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Final, 4.3.1.Final, 4.4.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > > Quoting [~paul.robinson] > {quote} > I noticed that JBDS is using this query to lookup available Quickstarts: > http://dcp.jboss.org/v1/rest/search?content_provider=jboss-developer&cont... > Fred, will keep me honest here. > I think you want to be aware of this as part of the decommissioning of DCP1 (dcp.jboss.org) now that we've moved to DCP2 (dcp2.jboss.org). > I presume this introduces challenges as we have installed software using this deprecated API on a deprecated server? > {quote} > {quote} > Looks like you can just switch the server and protocol bits of the URL: > http://dcp2.jboss.org/v2/rest/search?content_provider=jboss-developer&con... > {quote} > Unfortunately it seems we can't parse the new query output. We need to investigate whether the ouput can be made compatible with JBDS 9, or fall back to another solution (serve hard coded results? another alternative) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22456) DCP v1 API is phasing out, need to migrate to v2, ensure old JBDS versions will survive

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22456: ----------------------------------- Summary: DCP v1 API is phasing out, need to migrate to v2, ensure old JBDS versions will survive Key: JBIDE-22456 URL: https://issues.jboss.org/browse/JBIDE-22456 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.4.0.Alpha2, 4.3.1.Final, 4.3.0.Final Reporter: Fred Bricon Quoting [~paul.robinson] {quote} I noticed that JBDS is using this query to lookup available Quickstarts: http://dcp.jboss.org/v1/rest/search?content_provider=jboss-developer&cont... Fred, will keep me honest here. I think you want to be aware of this as part of the decommissioning of DCP1 (dcp.jboss.org) now that we've moved to DCP2 (dcp2.jboss.org). I presume this introduces challenges as we have installed software using this deprecated API on a deprecated server? {quote} {quote} Looks like you can just switch the server and protocol bits of the URL: http://dcp2.jboss.org/v2/rest/search?content_provider=jboss-developer&con... {quote} Unfortunately it seems we can't parse the new query output. We need to investigate whether the ouput can be made compatible with JBDS 9, or fall back to another solution (serve hard coded results? another alternative) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22456) DCP v1 API is phasing out, need to migrate to v2, ensure old JBDS versions will survive

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22456?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22456: -------------------------------- Priority: Blocker (was: Major) > DCP v1 API is phasing out, need to migrate to v2, ensure old JBDS versions will survive > --------------------------------------------------------------------------------------- > > Key: JBIDE-22456 > URL: https://issues.jboss.org/browse/JBIDE-22456 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Final, 4.3.1.Final, 4.4.0.Alpha2 > Reporter: Fred Bricon > Priority: Blocker > > Quoting [~paul.robinson] > {quote} > I noticed that JBDS is using this query to lookup available Quickstarts: > http://dcp.jboss.org/v1/rest/search?content_provider=jboss-developer&cont... > Fred, will keep me honest here. > I think you want to be aware of this as part of the decommissioning of DCP1 (dcp.jboss.org) now that we've moved to DCP2 (dcp2.jboss.org). > I presume this introduces challenges as we have installed software using this deprecated API on a deprecated server? > {quote} > {quote} > Looks like you can just switch the server and protocol bits of the URL: > http://dcp2.jboss.org/v2/rest/search?content_provider=jboss-developer&con... > {quote} > Unfortunately it seems we can't parse the new query output. We need to investigate whether the ouput can be made compatible with JBDS 9, or fall back to another solution (serve hard coded results? another alternative) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3884) Define the version of EAP that we embed with next major version of devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3884?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3884: ----------------------------- Description: EAP 7.0 will be in devstudio 10.0.0.Alpha3, but future releases may change the way packaging occurs. See linked Trello cards for Big Questions. (was: Should it continue to be EAP 6.x or the new EAP 7.0 ?) > Define the version of EAP that we embed with next major version of devstudio > ---------------------------------------------------------------------------- > > Key: JBDS-3884 > URL: https://issues.jboss.org/browse/JBDS-3884 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: runtime > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Assignee: Todd Mancini > Fix For: 10.x > > > EAP 7.0 will be in devstudio 10.0.0.Alpha3, but future releases may change the way packaging occurs. See linked Trello cards for Big Questions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3910) Include EAP 7.0 in JBDS installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3910?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3910: ---------------------------------- No longer blocked by Big Questions, which will be re-addressed for after 10.0.0.GA. > Include EAP 7.0 in JBDS installer > --------------------------------- > > Key: JBDS-3910 > URL: https://issues.jboss.org/browse/JBDS-3910 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Component Upgrade > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.0.0.Alpha3 > > > Include EAP 7.0.0 in JBDS 10 installer. Once ready, add it to http://www.jboss.org/products/devstudio/download/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-199) Docker Neon RC2 [EBZ#494053]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-199?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-199: --------------------------------- Assignee: Jeff Johnston > Docker Neon RC2 [EBZ#494053] > ---------------------------- > > Key: ERT-199 > URL: https://issues.jboss.org/browse/ERT-199 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6), Neon (4.6) RC2 > > > Release Docker as part of Linux Tools RC2 for Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-199) Docker Neon RC2 [EBZ#494053]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-199?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-199. ------------------------------- Fix Version/s: Neon (4.6) RC2 Resolution: Done > Docker Neon RC2 [EBZ#494053] > ---------------------------- > > Key: ERT-199 > URL: https://issues.jboss.org/browse/ERT-199 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6), Neon (4.6) RC2 > > > Release Docker as part of Linux Tools RC2 for Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-222: --------------------------------------- Summary: 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 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22453) Application Wizard: Shell to add and edit environment variable have different labels for name

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22453?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22453: ------------------------------------------ Fix Version/s: 4.4.0.Alpha3 (was: 4.4.x) > Application Wizard: Shell to add and edit environment variable have different labels for name > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22453 > URL: https://issues.jboss.org/browse/JBIDE-22453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > In New OpenShift Application wizard with selected builder image there is a table containing environment variables on the Build Configuration wizard page. When adding a new variable by clicking on Add... button, shell to add is opened with labels "Name:" and "Value:". When editing an environment variable on the same wizard page, there are different labels in edit env. var shell. Environment variable name is labeled as "Environment Variable:" and value as "Value:". It should be same for both dialogs, I would recommend labels Name and Value. > Same table with buttons seems to be used also in deploy docker image wizard, there is same flaw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22453) Application Wizard: Shell to add and edit environment variable have different labels for name

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22453?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22453: ------------------------------------------ Story Points: 1 Sprint: devex #115 May 2016 > Application Wizard: Shell to add and edit environment variable have different labels for name > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22453 > URL: https://issues.jboss.org/browse/JBIDE-22453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > In New OpenShift Application wizard with selected builder image there is a table containing environment variables on the Build Configuration wizard page. When adding a new variable by clicking on Add... button, shell to add is opened with labels "Name:" and "Value:". When editing an environment variable on the same wizard page, there are different labels in edit env. var shell. Environment variable name is labeled as "Environment Variable:" and value as "Value:". It should be same for both dialogs, I would recommend labels Name and Value. > Same table with buttons seems to be used also in deploy docker image wizard, there is same flaw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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