April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]

by Fred Bricon (JIRA)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]

by Fred Bricon (JIRA)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22240) Tests: frequent failures in ConnectionRegistryTest.shouldNotifyConnectionChange

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22240?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22240 at 4/22/16 7:23 PM: ------------------------------------------------------------------- The test never fails in Eclipse but with mvn in 1/3 builds in jenkins but 1/6 in my local mvn build. was (Author: adietish): The test never fails in Eclipse but with mvn in 1/3 builds. > Tests: frequent failures in ConnectionRegistryTest.shouldNotifyConnectionChange > ------------------------------------------------------------------------------- > > Key: JBIDE-22240 > URL: https://issues.jboss.org/browse/JBIDE-22240 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > > ConnectionRegistryTest.shouldNotifyConnectionChange is frequently (even though not always) failing when running tests via surefire. > {code} > shouldNotifyConnectionChange(org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest) Time elapsed: 0.002 sec <<< FAILURE! > java.lang.AssertionError: Exp. a notification to the listener and there was none > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest.shouldNotifyConnectionChange(ConnectionRegistryTest.java:142) > Failed tests: > ConnectionRegistryTest.shouldNotifyConnectionChange:142 Exp. a notification to the listener and there was none > Tests run: 314, Failures: 1, Errors: 0, Skipped: 2 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22240) Tests: frequent failures in ConnectionRegistryTest.shouldNotifyConnectionChange

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22240?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22240: ------------------------------------- Issue Type: Bug (was: Feature Request) > Tests: frequent failures in ConnectionRegistryTest.shouldNotifyConnectionChange > ------------------------------------------------------------------------------- > > Key: JBIDE-22240 > URL: https://issues.jboss.org/browse/JBIDE-22240 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > > ConnectionRegistryTest.shouldNotifyConnectionChange is frequently (even though not always) failing when running tests via surefire. > {code} > shouldNotifyConnectionChange(org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest) Time elapsed: 0.002 sec <<< FAILURE! > java.lang.AssertionError: Exp. a notification to the listener and there was none > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest.shouldNotifyConnectionChange(ConnectionRegistryTest.java:142) > Failed tests: > ConnectionRegistryTest.shouldNotifyConnectionChange:142 Exp. a notification to the listener and there was none > Tests run: 314, Failures: 1, Errors: 0, Skipped: 2 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3653: -------------------------------- Sprint: (was: devex #6 April 2016) > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha1 > > 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 (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22209?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22209: -------------------------------- Story Points: 1 > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift] > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22209 > URL: https://issues.jboss.org/browse/JBIDE-22209 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Rob Stryker > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [OpenShift]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-openshift at https://github.com/jbosstools/jbosstools-openshift/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "8e29d0" is the last common ancestor of jbosstools-4.3.x and master > 8e29d0 is 409 commits ago in branch master > 8e29d0 is 394 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-openshift//commit/9f74be7e9e62b7... false positive (https://github.com/jbosstools/jbosstools-openshift/commit/e95668e54ab2520...) > - https://github.com/jbosstools/jbosstools-openshift//commit/e0f8e68a563905... > - https://github.com/jbosstools/jbosstools-openshift//commit/009dcba545a46a... > - https://github.com/jbosstools/jbosstools-openshift//commit/fcdfc9a8da1d94... > - https://github.com/jbosstools/jbosstools-openshift//commit/087f63953adebe... > - https://github.com/jbosstools/jbosstools-openshift//commit/55c161d3adf09e... > - https://github.com/jbosstools/jbosstools-openshift//commit/2b7e853f34533c... > - https://github.com/jbosstools/jbosstools-openshift//commit/2aa9125ab7f7e9... > - https://github.com/jbosstools/jbosstools-openshift//commit/36cb020dbdb0f6... > - https://github.com/jbosstools/jbosstools-openshift//commit/7a2589b5e1f43f... > - https://github.com/jbosstools/jbosstools-openshift//commit/e77a887a382e2c... > - https://github.com/jbosstools/jbosstools-openshift//commit/eb65cd687d0002... > - https://github.com/jbosstools/jbosstools-openshift//commit/39492ed2137579... > - https://github.com/jbosstools/jbosstools-openshift//commit/6873d3b22fc734... > - https://github.com/jbosstools/jbosstools-openshift//commit/5c09968cfb3e07... > - https://github.com/jbosstools/jbosstools-openshift//commit/4f729326a186d0... > - https://github.com/jbosstools/jbosstools-openshift//commit/760a1f971fc17d... > - https://github.com/jbosstools/jbosstools-openshift//commit/7dffff362b99f4... > - https://github.com/jbosstools/jbosstools-openshift//commit/e7dde4151339ab... > - https://github.com/jbosstools/jbosstools-openshift//commit/1605d63e6d7e51... > - https://github.com/jbosstools/jbosstools-openshift//commit/26a1d1e7d91801... > - https://github.com/jbosstools/jbosstools-openshift//commit/5968aa42fac7ed... > - https://github.com/jbosstools/jbosstools-openshift//commit/95dac28be51c0e... > - https://github.com/jbosstools/jbosstools-openshift//commit/e4ecf6ff5ea331... > - https://github.com/jbosstools/jbosstools-openshift//commit/6c0cb8049b291e... > - https://github.com/jbosstools/jbosstools-openshift//commit/d6a2d2effd2a73... > - https://github.com/jbosstools/jbosstools-openshift//commit/8620c1caeeed74... > - https://github.com/jbosstools/jbosstools-openshift//commit/9b6e8d60ff1bf6... > - https://github.com/jbosstools/jbosstools-openshift//commit/f539d2ef0bee63... > - https://github.com/jbosstools/jbosstools-openshift//commit/2e3c64ced3c923... > - https://github.com/jbosstools/jbosstools-openshift//commit/201a855cc5cac7... > - https://github.com/jbosstools/jbosstools-openshift//commit/14b05efeef623a... > - https://github.com/jbosstools/jbosstools-openshift//commit/8c5a7ead1fa835... > - https://github.com/jbosstools/jbosstools-openshift//commit/213f368d88d215... > - https://github.com/jbosstools/jbosstools-openshift//commit/61a9b842a5c34a... > - https://github.com/jbosstools/jbosstools-openshift//commit/4206c33ba53c6f... > - https://github.com/jbosstools/jbosstools-openshift//commit/bd9c728c6c3a75... > - https://github.com/jbosstools/jbosstools-openshift//commit/f51830888169e7... > - https://github.com/jbosstools/jbosstools-openshift//commit/951590f4f5cf8d... > - https://github.com/jbosstools/jbosstools-openshift//commit/17da52cb6d9651... > - https://github.com/jbosstools/jbosstools-openshift//commit/2578624c74b744... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for OpenShift task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21187) Fix issues with styled label providers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21187?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21187: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) Story Points: 1 Sprint: devex #6 April 2016 > Fix issues with styled label providers > -------------------------------------- > > Key: JBIDE-21187 > URL: https://issues.jboss.org/browse/JBIDE-21187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Snjezana Peco > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > Attachments: bad-labels-tree.png, correct-labels-tree.png, openshift2-grey-decorations.png, openshift3-grey-decorations.png > > > Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 has been fixed, we can remove the workaround related to styled label providers. > The fix is included in Mars 4.5.1 (Mars.1) and Neon 4.6.0M2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3653: -------------------------------- Workaround Description: {color:red}use VAGRANT_HOME environment variable and set path to c:\DeveloperPlatform\vagrant\.vagrant.d or any location without spaces in name with write access for current user.{color} (was: {color:red}use VAGRANT_HOME environment variable and set path to c:\DeveloperPlatform\vagrant\.vagrant.d or any location without spaces in name.{color}) > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha1 > > 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 (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3818) Installer does not remember my selected folder until 'continue' is pressed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3818?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3818. --------------------------------- Resolution: Done > Installer does not remember my selected folder until 'continue' is pressed > -------------------------------------------------------------------------- > > Key: JBDS-3818 > URL: https://issues.jboss.org/browse/JBDS-3818 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > For some reason installer remembers the selected folder only if it reached the confirmation page. > Log in -> select a target folder -> go back to login -> log in again -> selected folder is back to default > Log in -> select a target folder -> continue -> go back to login -> log in again -> target folder stays the way it was selected -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22240) Tests: frequent failures in ConnectionRegistryTest.shouldNotifyConnectionChange

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22240?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22240 at 4/22/16 6:24 PM: ------------------------------------------------------------------- The test never fails in Eclipse but with mvn in 1/3 builds. was (Author: adietish): The test never fails in Eclipse but with mvn in 2 out of 3 builds. > Tests: frequent failures in ConnectionRegistryTest.shouldNotifyConnectionChange > ------------------------------------------------------------------------------- > > Key: JBIDE-22240 > URL: https://issues.jboss.org/browse/JBIDE-22240 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > > ConnectionRegistryTest.shouldNotifyConnectionChange is frequently (even though not always) failing when running tests via surefire. > {code} > shouldNotifyConnectionChange(org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest) Time elapsed: 0.002 sec <<< FAILURE! > java.lang.AssertionError: Exp. a notification to the listener and there was none > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest.shouldNotifyConnectionChange(ConnectionRegistryTest.java:142) > Failed tests: > ConnectionRegistryTest.shouldNotifyConnectionChange:142 Exp. a notification to the listener and there was none > Tests run: 314, Failures: 1, Errors: 0, Skipped: 2 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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