April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22034) Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22034?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22034: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) > Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22034 > URL: https://issues.jboss.org/browse/JBIDE-22034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Currently console containing output of rsync contains Pin Console toggle item which is useless there. Item should be changed to Show Console Output When Standard Out Changes which, when is enabled, show console view when output in it changes - this makes sense because if user want to track what have been rsynced, this is nice way to do it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3838) Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3838?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3838. --------------------------------- Resolution: Done > Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3838 > URL: https://issues.jboss.org/browse/JBDS-3838 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: install.log, vagrant.log, vbox.log > > -- 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 commented on JBIDE-22240: ------------------------------------------ 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

[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 updated JBIDE-22240: ------------------------------------- Sprint: devex #6 April 2016 > 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)

Andre Dietisheim created JBIDE-22240: ---------------------------------------- Summary: 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 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: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > 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 > 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 reassigned JBIDE-22240: ---------------------------------------- Assignee: Andre Dietisheim > 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-22235) NullPointerException in BarrierProgressWaitJob.canceling

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22235?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22235: -------------------------------- Sprint: devex #6 April 2016 > NullPointerException in BarrierProgressWaitJob.canceling > -------------------------------------------------------- > > Key: JBIDE-22235 > URL: https://issues.jboss.org/browse/JBIDE-22235 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.canceling(BarrierProgressWaitJob.java:143) > at org.eclipse.core.internal.jobs.InternalJob.cancel(InternalJob.java:185) > at org.eclipse.core.runtime.jobs.Job.cancel(Job.java:220) > at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.monitorSafeJoin(BarrierProgressWaitJob.java:135) > at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:330) > at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:319) > at org.jboss.tools.foundation.core.ecf.internal.URLTransportCache.downloadAndCache(URLTransportCache.java:177) > at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:186) > at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:88) > at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:244) > at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadProperties(VersionPropertiesProvider.java:271) > at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:151) > at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamplesUrl(ProjectExampleJsonProvider.java:141) > at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamples(ProjectExampleJsonProvider.java:55) > at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.0.1.Final-v20160401-1059-B103 | > | org.jboss.tools.foundation.core | 1.2.1.Final-v20160408-2358-B112 | 1.2.1.Final-v20160408-2358-B112 | > | org.jboss.tools.project.examples | 3.0.1.Final-v20160401-1059-B103 | 3.0.1.Final-v20160401-1059-B103 | > Operating Systems: > | Windows | 6.1.0 | 6.1.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a1ed7e4b0e9dd9c...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3853) Installer: use node-rcedit instead of resourceHacker

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3853?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3853: ----------------------------------- Assignee: Denis Golovin > Installer: use node-rcedit instead of resourceHacker > ---------------------------------------------------- > > Key: JBDS-3853 > URL: https://issues.jboss.org/browse/JBDS-3853 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > Installer's metadata and icon are changed by Gulp using Resource Hacker which requires that we manually pre-compile its configuration on every change in metadata (e.g. project version). > Change it to node-rcedit module (already used by electron-packager to do the same thing for binary inside self-extracting zip) -- 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