October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23353) Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23353?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23353: ---------------------------------------- Assignee: Viacheslav Kabanovich > Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click > ----------------------------------------------------------------------------- > > Key: JBIDE-23353 > URL: https://issues.jboss.org/browse/JBIDE-23353 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > In Deploy Image to OpenShift on wizard page with routing settings there is a table with port mapping. There is a table cell with checkbox to be used by routing. This is not editable by clicking on the cell. User is forced to open dialog to edit port mapping, manually click on a checkbox to use for routing and confirm dialog. This is pretty user unfriendly. It should be enabled to click on the cell and have checkbox checked/unchecked. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23353) Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23353?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23353: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1350, https://github.com/jbosstools/jbosstools-openshift/pull/1357 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1350) > Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click > ----------------------------------------------------------------------------- > > Key: JBIDE-23353 > URL: https://issues.jboss.org/browse/JBIDE-23353 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > In Deploy Image to OpenShift on wizard page with routing settings there is a table with port mapping. There is a table cell with checkbox to be used by routing. This is not editable by clicking on the cell. User is forced to open dialog to edit port mapping, manually click on a checkbox to use for routing and confirm dialog. This is pretty user unfriendly. It should be enabled to click on the cell and have checkbox checked/unchecked. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23353) Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23353?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23353: ------------------------------------------ merged into master > Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click > ----------------------------------------------------------------------------- > > Key: JBIDE-23353 > URL: https://issues.jboss.org/browse/JBIDE-23353 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > In Deploy Image to OpenShift on wizard page with routing settings there is a table with port mapping. There is a table cell with checkbox to be used by routing. This is not editable by clicking on the cell. User is forced to open dialog to edit port mapping, manually click on a checkbox to use for routing and confirm dialog. This is pretty user unfriendly. It should be enabled to click on the cell and have checkbox checked/unchecked. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23370: ------------------------------------ PR applied in both 4.60.x and 4.61.x branches. Building... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=591 > Update RedDeer in TP for JBT 4.4.2.AM3 > -------------------------------------- > > Key: JBIDE-23370 > URL: https://issues.jboss.org/browse/JBIDE-23370 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. > This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released. > We will want to update RedDeer in the TP to include the latest from > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP. > So please let me know when you're ready for this task and then I can create the update site immediately. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23413) use Import-Package instead of Require-Bundle for slf4j.api [hibernate]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23413?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23413 at 10/25/16 2:37 PM: -------------------------------------------------------------- Possible PR: https://github.com/jbosstools/jbosstools-hibernate/pull/120 However, I can't seem to make all the hibernate tests pass locally. So not sure if this is a better/worse thing. {code} [INFO] org.hibernate.eclipse .............................. SUCCESS [ 1.710 s] ... [INFO] org.hibernate.eclipse.feature ...................... FAILURE [ 0.564 s] ... [INFO] org.hibernate.eclipse.console.test ................. FAILURE [01:40 min] {code} Also, seems like you only depend on 2 classes in the whole bundle - both for logging. So you might not need to import all three packages. Perhaps you only need a PR like this one? https://github.com/jbosstools/jbosstools-livereload/pull/134/files was (Author: nickboldt): Possible PR: https://github.com/jbosstools/jbosstools-hibernate/pull/120 However, I can't seem to make all the hibernate tests pass locally. So not sure if this is a better/worse thing. {code} [INFO] org.hibernate.eclipse .............................. SUCCESS [ 1.710 s] ... [INFO] org.hibernate.eclipse.feature ...................... FAILURE [ 0.564 s] ... [INFO] org.hibernate.eclipse.console.test ................. FAILURE [01:40 min] {code} > use Import-Package instead of Require-Bundle for slf4j.api [hibernate] > ---------------------------------------------------------------------- > > Key: JBIDE-23413 > URL: https://issues.jboss.org/browse/JBIDE-23413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.4.2.AM3 > > Attachments: org.hibernate.eclipse.unresolved.req.txt > > > Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23413) use Import-Package instead of Require-Bundle for slf4j.api [hibernate]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23413?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23413: ------------------------------------ Possible PR: https://github.com/jbosstools/jbosstools-hibernate/pull/120 However, I can't seem to make all the hibernate tests pass locally. So not sure if this is a better/worse thing. {code} [INFO] org.hibernate.eclipse .............................. SUCCESS [ 1.710 s] ... [INFO] org.hibernate.eclipse.feature ...................... FAILURE [ 0.564 s] ... [INFO] org.hibernate.eclipse.console.test ................. FAILURE [01:40 min] {code} > use Import-Package instead of Require-Bundle for slf4j.api [hibernate] > ---------------------------------------------------------------------- > > Key: JBIDE-23413 > URL: https://issues.jboss.org/browse/JBIDE-23413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.4.2.AM3 > > Attachments: org.hibernate.eclipse.unresolved.req.txt > > > Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23030: ------------------------------------- Comment: was deleted (was: [~jeffmaury] [~bdshadow] Can one of you please chime in here so that we can have this fixed for the next release?) > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22362: ------------------------------------------ [~jeffmaury] [~bdshadow] Can one of you please chime in here so that we can have this fixed for the next release? > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM3 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23030: ------------------------------------------ [~jeffmaury] [~bdshadow] Can one of you please chime in here so that we can have this fixed for the next release? > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23414) use Import-Package instead of Require-Bundle for slf4j.api [central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23414?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-23414. --------------------------------- Resolution: Done GWT feature & plugin removed from repo. > use Import-Package instead of Require-Bundle for slf4j.api [central] > -------------------------------------------------------------------- > > Key: JBIDE-23414 > URL: https://issues.jboss.org/browse/JBIDE-23414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.2.AM3 > > > Because central use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-central/blob/fc4bfc7aea223c95b71... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 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 October 2016