July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22693) Label for editing name of property in design view is too short. Name seems to be cut.

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22693?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22693: ----------------------------------------------- I opened issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=497596 > Label for editing name of property in design view is too short. Name seems to be cut. > ------------------------------------------------------------------------------------- > > Key: JBIDE-22693 > URL: https://issues.jboss.org/browse/JBIDE-22693 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: xml-structured-editor > Environment: devstudio: > Version: 10.0.1.AM1 > Build id: v20160613-2041 > Fedora 24, x86_64 > Reporter: Ondrej Dockal > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > Attachments: DesignView1_Batch.png, DesignView2_Batch.png, DesignView3_Batch.png > > > Implies to editing label component in all property tables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-337) Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-337: --------------------------------------- Summary: Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532] Key: ERT-337 URL: https://issues.jboss.org/browse/ERT-337 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Currently dynamic parser model is used for from-end debugging (Web Inspector Protocol) which is incompatible with new versions of blink / chromium. Need to switch to static parser model which is claimed to have backward compatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-22686: ------------------------------------------- So is your host actually up? Can you {code}vagrant ssh{code}? Do you use a different IP? Something is fishy here. > Can't push image to docker registry > ----------------------------------- > > Key: JBIDE-22686 > URL: https://issues.jboss.org/browse/JBIDE-22686 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Environment: Fedora 23 > Reporter: Dmitry Bocharov > Assignee: Dmitry Bocharov > Fix For: 4.4.x > > Attachments: DeployDockerImageToOS.webm > > > The screencast of the last steps is attached. > Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way. > Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings. > _exception:_ > org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ > v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused > v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047) > at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ > v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused > v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused > at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42) > at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74) > at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043) > ... 3 more > Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ > v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused > v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused > at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49) > at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40) > ... 6 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22702) Decorators are shifted after selecting an element in combo which displays a submessage

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22702?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22702: ----------------------------------------- Confirmed, if you resize the dialog the decorator is correctly placed > Decorators are shifted after selecting an element in combo which displays a submessage > -------------------------------------------------------------------------------------- > > Key: JBIDE-22702 > URL: https://issues.jboss.org/browse/JBIDE-22702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: Aurélien Pupier > Attachments: after.png, before.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22702) Decorators are shifted after selecting an element in combo which displays a submessage

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22702?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22702: ----------------------------------------- It seems that's a Windows only issue. Can you reproduce that on OS/X? > Decorators are shifted after selecting an element in combo which displays a submessage > -------------------------------------------------------------------------------------- > > Key: JBIDE-22702 > URL: https://issues.jboss.org/browse/JBIDE-22702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: Aurélien Pupier > Attachments: after.png, before.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22702) Decorators are shifted after selecting an element in combo which displays a submessage

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22702?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-22702: ----------------------------------------- Windows 10 > Decorators are shifted after selecting an element in combo which displays a submessage > -------------------------------------------------------------------------------------- > > Key: JBIDE-22702 > URL: https://issues.jboss.org/browse/JBIDE-22702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: Aurélien Pupier > Attachments: after.png, before.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22702) Decorators are shifted after selecting an element in combo which displays a submessage

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22702?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22702: ----------------------------------------- What OS are you testing? I can't reproduce on Fedora 24 > Decorators are shifted after selecting an element in combo which displays a submessage > -------------------------------------------------------------------------------------- > > Key: JBIDE-22702 > URL: https://issues.jboss.org/browse/JBIDE-22702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: Aurélien Pupier > Attachments: after.png, before.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22696 at 7/8/16 11:48 AM: ------------------------------------------------------------- Branded Product now has correct qualifier (AM1-current-date). About box has correct ID and date. Core features feature has the current time (because of this latest commit). Capabilities feature has date of 06/08 (because that's when it was last updated). Screenshot of local build: [^jbide22696.png] Should be the same when built in Jenkins, except the B### number will be present too. was (Author: nickboldt): Branded Product now has correct qualifier (AM1-current-date). About box has correct ID and date. Core features feature has the current time (because of this latest commit). Capabilities feature has date of 06/08 (because that's when it was last updated). [^jbide22696.png] > jbosstools and devstudio sites / installer use old timestamps > ------------------------------------------------------------- > > Key: JBIDE-22696 > URL: https://issues.jboss.org/browse/JBIDE-22696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.1.AM2 > > Attachments: devstudio10.01.png, jbide22696.png, jbt441.png > > > Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22696 at 7/8/16 11:48 AM: ------------------------------------------------------------- Branded Product now has correct qualifier (AM1-current-date). About box has correct ID and date. Core features feature has the current time (because of this latest commit). Capabilities feature has date of 06/08 (because that's when it was last updated). Screenshot of local build: [^jbide22696.png] Should be the same when built in Jenkins, except the B5639 (or later) number will be present too. was (Author: nickboldt): Branded Product now has correct qualifier (AM1-current-date). About box has correct ID and date. Core features feature has the current time (because of this latest commit). Capabilities feature has date of 06/08 (because that's when it was last updated). Screenshot of local build: [^jbide22696.png] Should be the same when built in Jenkins, except the B### number will be present too. > jbosstools and devstudio sites / installer use old timestamps > ------------------------------------------------------------- > > Key: JBIDE-22696 > URL: https://issues.jboss.org/browse/JBIDE-22696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.1.AM2 > > Attachments: devstudio10.01.png, jbide22696.png, jbt441.png > > > Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-22696. -------------------------------- Resolution: Done > jbosstools and devstudio sites / installer use old timestamps > ------------------------------------------------------------- > > Key: JBIDE-22696 > URL: https://issues.jboss.org/browse/JBIDE-22696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.1.AM2 > > Attachments: devstudio10.01.png, jbide22696.png, jbt441.png > > > Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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