November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4123) Progress sometimes not updating for multiple file downloads

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4123?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4123: ------------------------------ Fix Version/s: 10.2.0.GA (was: 10.2.0.AM3) > Progress sometimes not updating for multiple file downloads > ----------------------------------------------------------- > > Key: JBDS-4123 > URL: https://issues.jboss.org/browse/JBDS-4123 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.2.0.GA > > > Namely for CDK, sometimes the progress doesn't register that it should start. The handler that should set the correct values does not seem to fire properly every time. The result is a progress bar stuck on 0% for the entirety of the download. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4123) Progress sometimes not updating for multiple file downloads

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4123?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4123: ------------------------------ Sprint: devex #123 November 2016 (was: devex #122 October 2016) > Progress sometimes not updating for multiple file downloads > ----------------------------------------------------------- > > Key: JBDS-4123 > URL: https://issues.jboss.org/browse/JBDS-4123 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.2.0.GA > > > Namely for CDK, sometimes the progress doesn't register that it should start. The handler that should set the correct values does not seem to fire properly every time. The result is a progress bar stuck on 0% for the entirety of the download. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-3653: --------------------------------------- FYI The only reference of Ruby with this issue is this bug: https://bugs.ruby-lang.org/issues/7036 which is marked as fixed for several years. I put a comment on the Vagrant https://github.com/mitchellh/vagrant/issues/4351#issuecomment-258376266 related issue. Currently the implementation of Vagrant is not even trying to install plugins when it detects space in path: https://github.com/mitchellh/vagrant/blob/9c299a2a357fcf87f356bb9d56e18a0... I don't know if there are some Vagrant and/or Ruby guys @Red Hat that can help to sort out this issue. > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23170) Red Hat Central page auto-resizing gets broken after editing options

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23170?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23170. ------------------------------ Resolution: Done Resolving & closing (verified by Denis) > Red Hat Central page auto-resizing gets broken after editing options > -------------------------------------------------------------------- > > Key: JBIDE-23170 > URL: https://issues.jboss.org/browse/JBIDE-23170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.Final > Environment: Windows 10 Home > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.4.2.AM3 > > Attachments: 2016 09 14 2223 34.mp4, jbosstools-central-webpage-2.0.0-SNAPSHOT.zip > > > I noticed sometimes Red Hat Central stops resizing to editor part size and shows horizontal scrollbar. It happens when options button is clicked when editor part with central is maximized (see attached video). > !2016 09 14 2223 34.mp4! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23368: --------------------------------------- In that case it does not make sense to add new ports in the wizard page. Bcs. those ports listed in the table are obtained from docker image, adding additional ports would not make sense. I think ports in the table are retrieved from image metadata and if something went wrong and it was not retrieved, it would be bug on tooling side and we should fix it. But adding ports mapping does not make sense for me. > Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23368 > URL: https://issues.jboss.org/browse/JBIDE-23368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) > Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23368 at 11/4/16 4:35 AM: ------------------------------------------------------------------- [~mlabuda] the basic takeaway here is the following: the port mapping in the wizard is purely operating on the service. It wont open ports on the pods/containers, it just makes sure that the user can have service ports exposed. If those ports actually are backed by container ports (that are listened to and reachable: actual daemon running, port exposed via docker -p or -P) is not in the scope of this wizard. The wizard therefore should not add those ports to the replication controller, which operates pods. [~jcantrill] Can you please chime in and provide more details/insights? was (Author: adietish): [~mlabuda] the basic takeaway here is the following: the port mapping in the wizard is a purely operating on the service. It wont open ports on the ports, it just makes sure existing ports (that you can expose in the Dockerfile or when launching the container) are specified in the service. If those ports actually are backed by container ports (that are listened to and reachable) is not in the scope of this wizard. It's up to the developer to make sure the service ports are actually backed by the containers in the port. The wizard therefore should not add those ports to the replication controller, which operates pods. [~jcantrill] Can you please chime in and provide more details/insights? > Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23368 > URL: https://issues.jboss.org/browse/JBIDE-23368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) > Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23368: ------------------------------------------ [~mlabuda] the basic takeaway here is the following: the port mapping in the wizard is a purely operating on the service. It wont open ports on the ports, it just makes sure existing ports (that you can expose in the Dockerfile or when launching the container) are specified in the service. If those ports actually are backed by container ports (that are listened to and reachable) is not in the scope of this wizard. It's up to the developer to make sure the service ports are actually backed by the containers in the port. The wizard therefore should not add those ports to the replication controller, which operates pods. [~jcantrill] Can you please chime in and provide more details/insights? > Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23368 > URL: https://issues.jboss.org/browse/JBIDE-23368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) > Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23379) set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23379?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23379: ------------------------------------------ [~nickboldt] awesome, thanks! > set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23379 > URL: https://issues.jboss.org/browse/JBIDE-23379 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM3 > > > We should have a jenkins that builds [openshift-restclient-java|https://github.com/openshift/openshift-restclie...], deploys it to repository.jboss.org and triggers a rebuild of the [openshift client plugin|https://github.com/jbosstools/jbosstools-openshift/tree/master/plu...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23452) Webservices / Rest New and Noteworthy for 4.4.2.AM3

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23452?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23452. --------------------------------- Resolution: Rejected > Webservices / Rest New and Noteworthy for 4.4.2.AM3 > --------------------------------------------------- > > Key: JBIDE-23452 > URL: https://issues.jboss.org/browse/JBIDE-23452 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Webservices / Rest JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Webservices / Rest, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Webservices / Rest by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Webservices / Rest4.4.2.AM3 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Webservices / Rest for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23462) LiveReload New and Noteworthy for 4.4.2.AM3

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23462?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23462. --------------------------------- Resolution: Rejected > LiveReload New and Noteworthy for 4.4.2.AM3 > --------------------------------------------------- > > Key: JBIDE-23462 > URL: https://issues.jboss.org/browse/JBIDE-23462 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed LiveReload JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for LiveReload, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for LiveReload by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for LiveReload4.4.2.AM3 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for LiveReload for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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