March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21852) Use {noformat} tag for the stacktrace when creating a new JIRA

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21852?page=com.atlassian.jira.plugi... ] Marcel Bruch commented on JBIDE-21852: -------------------------------------- Makes sense for Jira. Added the {noformat} tags around stack trace template calls: {noformat} ${status.exception!} {noformat} > Use {noformat} tag for the stacktrace when creating a new JIRA > -------------------------------------------------------------- > > Key: JBIDE-21852 > URL: https://issues.jboss.org/browse/JBIDE-21852 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Aurélien Pupier > Fix For: 4.3.1.CR1 > > > For an example see https://issues.jboss.org/browse/FUSETOOLS-1702 > around the stacktrace, it would be nice to have {noformat} tags, it will help having a better description with a too long scrolldown to see detains of the report. it will display the stacktrac like that: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-21836 at 3/11/16 10:41 AM: ----------------------------------------------------------------------- I'm not creating a new workspace, just recreating eclipse. And oomph preferenced recorder is not enabled. was (Author: maxandersen): I'm not creating a new workspace, just recreating eclipse. > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Priority: Blocker > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.3.1.CR1 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-21836: ------------------------------------------- Assignee: Max Rydahl Andersen > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.3.1.CR1 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21836: --------------------------------------------- I'm not creating a new workspace, just recreating eclipse. > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Priority: Blocker > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.3.1.CR1 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen edited comment on JBDS-3650 at 3/11/16 10:38 AM: --------------------------------------------------------------------- [~dgolovin] was this not fixed so when you download CDK you get the right user permsisions ? was (Author: maxandersen): [~dgolovin] was this not fixed ? > username used for cdk could not be used with vagrant up on cdk > -------------------------------------------------------------- > > Key: JBDS-3650 > URL: https://issues.jboss.org/browse/JBDS-3650 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Reporter: Max Rydahl Andersen > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration. > Why is that ? just unique for denis usernames or general problem ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3650: -------------------------------------- Fix Version/s: 9.1.0.CR1 > username used for cdk could not be used with vagrant up on cdk > -------------------------------------------------------------- > > Key: JBDS-3650 > URL: https://issues.jboss.org/browse/JBDS-3650 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Reporter: Max Rydahl Andersen > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration. > Why is that ? just unique for denis usernames or general problem ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3650: ------------------------------------------- [~dgolovin] was this not fixed ? > username used for cdk could not be used with vagrant up on cdk > -------------------------------------------------------------- > > Key: JBDS-3650 > URL: https://issues.jboss.org/browse/JBDS-3650 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Reporter: Max Rydahl Andersen > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration. > Why is that ? just unique for denis usernames or general problem ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21849: --------------------------------------- [~xiazhao2015] can you list your projects and buildconfigs using oc: {{ `oc get projects` `oc get bc -n xia` }} > [AP] Not able to list services under a project after login to AP > ---------------------------------------------------------------- > > Key: JBIDE-21849 > URL: https://issues.jboss.org/browse/JBIDE-21849 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191 > -AP puddle: 2016-03-09.2 > -oc version: > oc v3.2.0.1 > kubernetes v1.2.0-alpha.7-703-gbc4550d > Reporter: Xia Zhao > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3 > > -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}" > -Issue did not repro if switch to OSE > -Repro on Linux/Windows/Mac OS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21700) Listen to pod redeployment after changing deployment configuration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21700?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21700: ----------------------------------- Assignee: Fred Bricon (was: Jeff Cantrill) > Listen to pod redeployment after changing deployment configuration > ------------------------------------------------------------------ > > Key: JBIDE-21700 > URL: https://issues.jboss.org/browse/JBIDE-21700 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > We need an easy way to detect a deployment configuration change triggered a new deployment and then be notified of its completion -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21702) For Java projects, automatically attach a remote debugger to the OpenShift debug port

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21702?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21702: ----------------------------------- Assignee: Fred Bricon (was: Rob Stryker) > For Java projects, automatically attach a remote debugger to the OpenShift debug port > ------------------------------------------------------------------------------------- > > Key: JBIDE-21702 > URL: https://issues.jboss.org/browse/JBIDE-21702 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > Given a local debug port, we should automatically attach a remote debugger to that port (similar to what is described in http://tools.jboss.org/documentation/howto/openshift_debug.html#idedebugger) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016