March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24411) Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24411?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24411: ------------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) > Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24411 > URL: https://issues.jboss.org/browse/JBIDE-24411 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.5.3.Final > > > Currently if I have an OpenSHift connection in OpenSHift Explorer which have bad credentials, if I expand it i have a little error message in the tree (which is nice) > So I right-click -> Edit connection... I update my connection parameters and when I click finish, in the tree I still have the error. I need to manually right-click -> refresh. > it would be nice to refresh automatically the tree when the connection has been edited -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Sprint: devex #147 April 2018 > [release] externalize common properties to parameterize jobs > ------------------------------------------------------------ > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-24799. -------------------------------- Resolution: Won't Do > [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.3.AM3 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24311) Application wizard: is loading templates even if I go back

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24311?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24311: ------------------------------------- Issue Type: Enhancement (was: Bug) > Application wizard: is loading templates even if I go back > ---------------------------------------------------------- > > Key: JBIDE-24311 > URL: https://issues.jboss.org/browse/JBIDE-24311 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24311) Application wizard: is loading templates even if I go back

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24311?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24311: ------------------------------------- Description: # ASSERT: have a openshift server (using the internal instance works better since it's remote, requests take more time) # EXEC: launch application wizard # EXEC: select a template and hit "Next >" and end up in the "Template Parameters" page # EXEC: hit "< Back" Result: page "Select Template" is displayed, mouse turns "hoursglass" and the page shows a progress bar indicating that the page is loading it's resources. Expected result: the page "Select Template" should only load upon initial display. Every subsequent display of the very same page should used cached resources, not load them again and again. > Application wizard: is loading templates even if I go back > ---------------------------------------------------------- > > Key: JBIDE-24311 > URL: https://issues.jboss.org/browse/JBIDE-24311 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.5.x > > > # ASSERT: have a openshift server (using the internal instance works better since it's remote, requests take more time) > # EXEC: launch application wizard > # EXEC: select a template and hit "Next >" and end up in the "Template Parameters" page > # EXEC: hit "< Back" > Result: > page "Select Template" is displayed, mouse turns "hoursglass" and the page shows a progress bar indicating that the page is loading it's resources. > Expected result: > the page "Select Template" should only load upon initial display. Every subsequent display of the very same page should used cached resources, not load them again and again. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24311) Application wizard: is loading templates even if I go back

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24311?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24311: ------------------------------------- Steps to Reproduce: (was: # ASSERT: have a openshift server (using the internal instance works better since it's remote, requests take more time) # EXEC: launch application wizard # EXEC: select a template and hit "Next >" and end up in the "Template Parameters" page # EXEC: hit "< Back" Result: page "Select Template" is displayed, mouse turns "hoursglass" and the page shows a progress bar indicating that the page is loading it's resources. Expected result: the page "Select Template" should only load upon initial display. Every subsequent display of the very same page should used cached resources, not load them again and again.) > Application wizard: is loading templates even if I go back > ---------------------------------------------------------- > > Key: JBIDE-24311 > URL: https://issues.jboss.org/browse/JBIDE-24311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24185: ------------------------------------- Issue Type: Enhancement (was: Bug) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24185: ------------------------------------- Issue Type: Task (was: Enhancement) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Description: I deployed the Camel Fuse Teampltes available in Fuse Tooling I restarted my Eclipse I reconnected to the same CDK - select application in OpenShift Instance view - go to Build Configs tab in properties view - select the element available Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) alternatively: * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... * create an app using the s2i-spring-boot-camel-xml template * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. steps: # I deployed the Camel Fuse Teampltes available in Fuse Tooling # I restarted my Eclipse # I reconnected to the same CDK # - select application in OpenShift Instance view # - go to Build Configs tab in properties view # - select the element available # Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) was: I deployed the Camel Fuse Teampltes available in Fuse Tooling I restarted my Eclipse I reconnected to the same CDK - select application in OpenShift Instance view - go to Build Configs tab in properties view - select the element available Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) alternatively: * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... * create an app using the s2i-spring-boot-camel-xml template * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.x > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. > steps: > # I deployed the Camel Fuse Teampltes available in Fuse Tooling > # I restarted my Eclipse > # I reconnected to the same CDK > # - select application in OpenShift Instance view > # - go to Build Configs tab in properties view > # - select the element available > # Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Issue Type: Feature Request (was: Bug) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.x > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2018