May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22458) JBoss Help should use DCP v2

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22458: ----------------------------------- Summary: JBoss Help should use DCP v2 Key: JBIDE-22458 URL: https://issues.jboss.org/browse/JBIDE-22458 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, common/jst/core Affects Versions: 4.4.0.Alpha1 Reporter: Fred Bricon The DCPv1 search service is being phased out in favor of DCPv2. The JBoss Help feature needs to migrate to v2 as well. - the search url needs to be changed to http://dcp2.jboss.org/v2/rest/search?size=100&query={expression}&sys_type... in org.jboss.tools.central/plugin.xml - The JSON Parser needs to be updated to the new result format (fields are returned as arrays, we need to get the 1st element now). See https://github.com/jbosstools/jbosstools-base/blob/e0b10e225f070bc11aa1bf... Bad news is JBDS 9/ JBT 4.3 help search will break as soon as DCPv1 is decommissioned, since the search URL is hard coded in the plugin.xml -- 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 resolved ERT-222. --------------------------------- Resolution: Done Marking as RESOLVED since this has been fixed, and will be targeting 5.0 (RC3) > 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] (JBIDE-22457) Template are not displayed in property views for an Openshift project

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22457: ---------------------------------- Summary: Template are not displayed in property views for an Openshift project Key: JBIDE-22457 URL: https://issues.jboss.org/browse/JBIDE-22457 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha2 Reporter: Jeff MAURY Fix For: 4.4.x Server template are not displayed in a specific tab for an Openshift project. This would be useful mainly for editing or creating new templates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22448) TP p2diff generation fails build when TP version changes

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22448?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22448: ------------------------------------ So you're saying you'd rather have to EXPLICITLY use the skip flag every time we upversion than assume that a 404'd reference site = new version? > TP p2diff generation fails build when TP version changes > -------------------------------------------------------- > > Key: JBIDE-22448 > URL: https://issues.jboss.org/browse/JBIDE-22448 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > Add support for skipping p2diff generation when there's no previous site against which to diff, eg., when upversioning or releasing from snapshot to release in Nexus. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3897) Use "Red Hat JBoss Developer Studio" instead of "Red Hat Developer Studio" in graphics

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3897?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3897: ---------------------------------- Assets are great (though two were the wrong filetype, which I fixed). https://github.com/jbdevstudio/jbdevstudio-product/commit/c82a52cf8c1f42c... https://github.com/jbdevstudio/jbdevstudio-product/commit/f5d0c207bbe0444... https://github.com/jbdevstudio/jbdevstudio-website/commit/22053b727197e5d... https://github.com/jbdevstudio/jbdevstudio-artwork/commit/63d0d40ff21050a... > Use "Red Hat JBoss Developer Studio" instead of "Red Hat Developer Studio" in graphics > -------------------------------------------------------------------------------------- > > Key: JBDS-3897 > URL: https://issues.jboss.org/browse/JBDS-3897 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha3 > > Attachments: about_devstudio.jpg, devstudio_banner.png, heading.png, RHJBoss_DevStudio_Assets.zip, splash.bmp > > > Due to changes in https://trello.com/c/Cbo0q8TT/99-rebrand-jbds-as-rhds-using-rhd-logo the correct name of the product is "Red Hat JBoss Developer Studio", not "Red Hat Developer Studio", so we need to add the "JBoss" part back into the new RHD-branded headers & splash. -- 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 commented on JBDS-3905: ---------------------------------- Please provide steps to do to verify it's working as you'd expect. "Should provide validation" and "no errors in the log" aren't detailed enough. Or, check out my PR, build it locally, install from the resulting installer in jbdevstudio-product/installer/target/*.jar, and let me know your results. > 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-3899) Include latest wst.jsdt and chromium.debug features in TPs, jboss tools, and devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3899?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3899: ---------------------------------- PRs above merged and building: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=5450 > Include latest wst.jsdt and chromium.debug features in TPs, jboss tools, and devstudio > -------------------------------------------------------------------------------------- > > Key: JBDS-3899 > URL: https://issues.jboss.org/browse/JBDS-3899 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > New JSDT included new Debugger plugins. They are not included in JSDT feature afaik. > We should make sure we have all needed plugins/features included in devstudio and JBT TPs/market place/installation. > [~vrubezhny], [~ibuziuk] please provide all needed info for [~nickboldt]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3913) EAP standalone.sh script is not executable in Dev Studio installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3913?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3913: ------------------------------- Attachment: 1.png 2.png > EAP standalone.sh script is not executable in Dev Studio installer > ------------------------------------------------------------------ > > Key: JBDS-3913 > URL: https://issues.jboss.org/browse/JBDS-3913 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Environment: http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.pro... > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Attachments: 1.png, 2.png > > > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3913) EAP standalone.sh script is not executable in Dev Studio installer

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3913: ---------------------------------- Summary: EAP standalone.sh script is not executable in Dev Studio installer Key: JBDS-3913 URL: https://issues.jboss.org/browse/JBDS-3913 Project: Red Hat Developer Studio (DevStudio) Issue Type: Bug Components: installer Environment: http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.pro... Reporter: Len DiMaggio Assignee: Nick Boldt Priority: Blocker See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[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 edited comment on JBDS-3909 at 5/27/16 3:08 PM: -------------------------------------------------------------- [~sjcox] Could you update .svg today? was (Author: dgolovin): [~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

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